VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

libav: vulnerability history, versions and safety

libav is a package in the Debian ecosystem. Vulert records 14 vulnerabilities for it across 21 releases, from Jun 2015 to Dec 2019. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
14 vulnerabilities recorded U14
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 libav vulnerabilities

Vulert verdict on libav i

Updated on 23 Oct 2026

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

Long-term outlook: usable, with an upgrade 14 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 14 over 4 years · 0 in the last year i
  • Latest disclosure 05 Dec 2019 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 libav, 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.

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2015 1
  • 2016 2
  • 2017 2
  • 2018 3
  • 2019 6

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

03 Vulnerabilities

Recorded vulnerabilities for libav

The 5 most severe of 14 vulnerabilities recorded for this package

Search all 14 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Security Update for libav N/A unrated 6:11.12-1~deb8u1 19 Feb 2018
Security Update for libav N/A unrated 6:11.8-1~deb8u1 04 Oct 2016
Security Update for libav N/A unrated 6:11.9-1~deb8u1 24 Apr 2017
Security Update for libav N/A unrated 6:11.11-1~deb8u1 31 Oct 2017
Security Update for libav N/A unrated 6:11.7-1~deb8u1 14 Jun 2016

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 libav

Is libav safe to use?

Vulert records 14 vulnerabilities for libav in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 14 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 libav have?

14 vulnerabilities are recorded for libav in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 14 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 libav vulnerabilities disclosed?

0 vulnerabilities were recorded for libav in the last 12 months, and the oldest entry in this database dates to 13 Jun 2015. 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 libav 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 libav for upcoming vulnerabilities?

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