VulertSecurity VulertSecurity

Vulnerability Database · OSS-Fuzz · Package report

libavif: vulnerability history, versions and safety

libavif is a package in the OSS-Fuzz ecosystem. Vulert records 11 vulnerabilities for it across 13 releases, from Jul 2020 to Jan 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
11 vulnerabilities recorded H3 M7 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 libavif vulnerabilities

Vulert verdict on libavif i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 05 Jan 2025. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 11 vulnerabilities on record across 4 years, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 11 over 4 years · 0 in the last year i
  • Latest disclosure 05 Jan 2025 i
  • Highest CVSS n/a i
  • With no published fix 0 i

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 holds for libavif, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
v0.8.1 H1 Yes Details →
v0.8.0 H1 Yes Details →
v0.7.2 M1 Yes Details →
v0.7.1 M1 Yes Details →
v0.7.0 M1 Yes Details →
v0.6.4 M1 Yes Details →
v0.6.3 M1 Yes Details →
v0.6.2 M1 Yes Details →
v0.6.1 M1 Yes Details →
v0.6.0 M1 Yes Details →
v0.5.7 M1 Yes Details →
v0.5.6 M1 Yes Details →
v0.5.5 M1 Yes Details →

Newest 13 of 13 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 5
  • 2024 3
  • 2025 3

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

03 Vulnerabilities

Recorded vulnerabilities for libavif

The 5 most severe of 11 vulnerabilities recorded for this package

Search all 11 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Heap-buffer-overflow in libavif: dav1dFeedData N/A medium 34c0d3147f3d30e1218bceda410c978481a5e1be 22 Jul 2020
UNKNOWN WRITE Vulnerability in libavif N/A high 0a8e7244d494ae98e9756355dfbfb6697ded2ff9 12 Aug 2020
Heap-buffer-overflow in avifROStreamRead in libavif N/A medium b86bc3c8296f7d37cacf674ee031851cd513b8e4 25 Sep 2020
Heap-use-after-free vulnerability in libavif N/A high 468ded88b6ee5ccc4ce1ed029a7d310e5764947c 25 Sep 2020
Vulnerability in libavif: UNKNOWN READ in avifRWDataSet N/A medium b86bc3c8296f7d37cacf674ee031851cd513b8e4 25 Sep 2020

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 libavif

Is libavif safe to use?

Vulert records 11 vulnerabilities for libavif in OSS-Fuzz: 0 critical, 3 high, 7 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.

How many vulnerabilities does libavif have?

11 vulnerabilities are recorded for libavif in the OSS-Fuzz ecosystem: 0 critical, 3 high, 7 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 libavif vulnerabilities disclosed?

0 vulnerabilities were recorded for libavif in the last 12 months, and the oldest entry in this database dates to 22 Jul 2020. 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 libavif 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 libavif for upcoming vulnerabilities?

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