VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

libafl: vulnerability history, versions and safety

libafl is a package in the crates.io ecosystem. Vulert records 2 vulnerabilities for it across 20 releases, first recorded in Dec 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded M1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all libafl vulnerabilities

Vulert verdict on libafl 0.16.1 i

Updated on 23 Oct 2026

Good news: 0.16.1, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 86/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

What to do: Stay on 0.16.1 or newer. This can change: a vulnerability disclosed tomorrow can affect 0.16.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 0.16.1 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 23 Dec 2024 i
  • Highest CVSS 6.9 i
  • With no published fix 0 i
  • Stars 2,663 i
  • Last release 2 months ago i
  • Licence Apache-2.0 OR MIT i

Version list, release dates, licence and dependants published by crates.io, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for libafl, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
0.16.1 11 Aug 2026 none Apache-2.0 OR MIT — Details →
0.16.0 11 Aug 2026 none Apache-2.0 OR MIT — Details →
0.15.4 12 Nov 2025 none Apache-2.0 OR MIT — Details →
0.15.3 29 May 2025 none Apache-2.0 OR MIT — Details →
0.15.2 29 Mar 2025 none Apache-2.0 OR MIT — Details →
0.15.1 05 Feb 2025 none Apache-2.0 OR MIT — Details →
0.15.0 20 Jan 2025 none Apache-2.0 OR MIT — Details →
0.14.1 02 Dec 2024 none Apache-2.0 OR MIT — Details →
0.14.0 13 Nov 2024 none Apache-2.0 OR MIT — Details →
0.13.2 31 Jul 2024 none Apache-2.0 OR MIT — Details →
0.13.1 30 Jun 2024 none Apache-2.0 OR MIT — Details →
0.13.0 14 Jun 2024 none Apache-2.0 OR MIT — Details →
0.12.0 12 Apr 2024 none Apache-2.0 OR MIT — Details →
0.11.2 21 Dec 2023 none Apache-2.0 OR MIT — Details →
0.11.1 31 Aug 2023 M1 U1 Apache-2.0 OR MIT Yes Details →
0.11.0 28 Aug 2023 M1 U1 Apache-2.0 OR MIT Yes Details →
0.10.1 24 May 2023 M1 U1 Apache-2.0 OR MIT Yes Details →
0.10.0 18 Apr 2023 M1 U1 Apache-2.0 OR MIT Yes Details →
0.9.0 31 Jan 2023 M1 U1 Apache-2.0 OR MIT Yes Details →
0.8.2 12 Oct 2022 M1 U1 Apache-2.0 OR MIT Yes Details →
0.8.1 18 Aug 2022 M1 U1 Apache-2.0 OR MIT Yes Details →
0.8.0 13 Jul 2022 M1 U1 Apache-2.0 OR MIT Yes Details →
0.7.1 13 Jan 2022 M1 U1 Apache-2.0 OR MIT Yes Details →
0.7.0 09 Dec 2021 M1 U1 Apache-2.0 OR MIT Yes Details →
0.6.1 23 Aug 2021 M1 U1 Apache-2.0 OR MIT Yes Details →
0.6.0 20 Aug 2021 M1 U1 Apache-2.0 OR MIT Yes Details →
0.5.0 05 Jul 2021 M1 U1 Apache-2.0 OR MIT Yes Details →
0.4.0 24 Jun 2021 M1 U1 Apache-2.0 OR MIT Yes Details →
0.3.2 20 May 2021 M1 U1 Apache-2.0 OR MIT Yes Details →
0.3.1 20 May 2021 M1 U1 Apache-2.0 OR MIT Yes Details →
0.3.0 19 May 2021 M1 U1 Apache-2.0 OR MIT Yes Details →
0.2.1 07 May 2021 M1 U1 Apache-2.0 OR MIT Yes Details →
0.2.0 06 May 2021 M1 U1 Apache-2.0 OR MIT Yes Details →
0.1.0 30 Apr 2021 M1 U1 Apache-2.0 OR MIT Yes Details →

All 34 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 2 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for libafl

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Unsound Memory Alignment Vulnerability in libafl 6.9 medium 0.11.2 23 Dec 2024
Unsound Memory Alignment Vulnerability in libafl N/A unrated 0.11.2 19 Dec 2024

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About libafl

Is libafl safe to use?

Vulert records 2 vulnerabilities for libafl in crates.io: 0 critical, 0 high, 1 medium and 0 low, plus 1 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is libafl's Vulert package health score?

Vulert scores libafl 86/100, which reads as healthy. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of libafl affected?

No. 0.16.1, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of libafl should I use?

0.16.1 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does libafl have?

2 vulnerabilities are recorded for libafl in the crates.io ecosystem: 0 critical, 0 high, 1 medium and 0 low, plus 1 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new libafl vulnerabilities disclosed?

0 vulnerabilities were recorded for libafl in the last 12 months, and the oldest entry in this database dates to 19 Dec 2024. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of libafl are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor libafl for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the libafl version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.