Vulnerability Database · Debian · Package report

ffmpeg: vulnerability history, versions and safety

ffmpeg is a package in the Debian ecosystem. Vulert records 692 vulnerabilities for it across 93 releases, from Nov -0001 to Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
692 vulnerabilities recorded U692
i
58 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
45 in the last 12 months

Most recent disclosure 28 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on ffmpeg i

Updated on 23 Oct 2026

Careful: 58 of the 692 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 692 vulnerabilities on record across 2026 years, 45 in the last year.

What to do: Plan around the 58 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 692 over 2026 years · 45 in the last year i
  • Latest disclosure 28 Aug 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 58 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 ffmpeg, 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
7:9.0.1-1 U15 No Details →
7:9.0-1 U15 No Details →
7:8.1-3 U43 No Details →
7:8.1.2-2 U39 No Details →
7:8.1.2-1 U39 No Details →
7:8.1-2 U43 No Details →
7:8.1.1-4 U40 No Details →
7:8.1.1-3 U40 No Details →
7:8.1.1-2 U40 No Details →
7:8.1.1-1 U40 No Details →
7:8.1-1 U43 No Details →
7:8.0-2 U44 No Details →
7:8.0.1-3 U43 No Details →
7:8.0.1-2 U44 No Details →
7:8.0.1-1 U44 No Details →
7:8.0-1 U52 No Details →
7:7.1-4 U57 No Details →
7:7.1.3-1 U44 No Details →
7:7.1-3 U58 No Details →
7:7.1.2-1 U52 No Details →
7:7.1-2 U58 No Details →
7:7.1.1-1 U57 No Details →
7:7.1-1 U58 No Details →
7:7.0.2-3 U58 No Details →
7:7.0.2-2 U58 No Details →
7:7.0.2-1 U58 No Details →
7:7.0.1-5 U58 No Details →
7:7.0.1-4 U58 No Details →
7:7.0.1-3 U58 No Details →
7:7.0.1-2 U58 No Details →
7:7.0.1-1 U58 No Details →
7:7.0-1 U58 No Details →
7:6.1-5 U58 No Details →
7:6.1-4 U58 No Details →
7:6.1-3 U58 No Details →
7:6.1-2 U58 No Details →
7:6.1.1-5 U58 No Details →
7:6.1.1-4 U58 No Details →
7:6.1.1-3 U58 No Details →
7:6.1.1-2 U58 No Details →
7:6.1.1-1 U58 No Details →
7:6.1-1 U58 No Details →
7:6.0-9 U58 No Details →
7:6.0-8 U58 No Details →
7:6.0-7 U58 No Details →
7:6.0-6 U58 No Details →
7:6.0-5 U58 No Details →
7:6.0-4 U58 No Details →
7:6.0-3 U58 No Details →
7:6.0-2 U58 No Details →
7:6.0-1 U58 No Details →
7:5.1.3-2 U58 No Details →
7:5.1.3-1 U58 No Details →
7:5.1-3 U58 No Details →
7:5.1.2-3 U58 No Details →
7:5.1.2-2 U58 No Details →
7:5.1-2.1 U58 No Details →
7:5.1.2-1 U58 No Details →
7:5.1-2 U58 No Details →
7:5.1.1-2 U58 No Details →
7:5.1.1-2+m68k U58 No Details →
7:5.1.1-1 U58 No Details →
7:5.1-1 U58 No Details →
7:5.0-3 U58 No Details →
7:5.0-2 U58 No Details →
7:5.0.1-3 U58 No Details →
7:5.0.1-2 U58 No Details →
7:5.0.1-1 U58 No Details →
7:5.0-1 U58 No Details →
7:4.4-6 U58 No Details →
7:4.4-5 U58 No Details →
7:4.4-4 U58 No Details →
7:4.4-3 U58 No Details →
7:4.4.2-1 U58 No Details →
7:4.4-2 U58 No Details →
7:4.4.1-3 U58 No Details →
7:4.4.1-2+ports U58 No Details →
7:4.4.1-2 U58 No Details →
7:4.4.1-1 U58 No Details →
7:4.4-1 U58 No Details →
7:4.3.9-0+deb11u2 U43 No Details →
7:4.3.9-0+deb11u1 U58 No Details →
7:4.3.8-0+deb11u3 U67 No Details →
7:4.3.8-0+deb11u2 U75 No Details →
7:4.3.8-0+deb11u1 U82 No Details →
7:4.3.7-0+deb11u1 U89 No Details →
7:4.3.6-0+deb11u1 U110 No Details →
7:4.3.5-0+deb11u1 U115 No Details →
7:4.3.4-0+deb11u1 U116 No Details →
7:4.3.3-0+deb11u1 U119 No Details →
7:4.3.2-2 U144 No Details →
7:4.3.2-1 U144 No Details →
7:4.3.2-0+deb11u2 U144 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 0 1
  • 2005 2
  • 2006 2
  • 2008 10
  • 2009 2
  • 2010 22
  • 2011 30
  • 2012 54
  • 2013 64
  • 2014 30
  • 2015 56
  • 2016 28
  • 2017 70
  • 2018 54
  • 2019 18
  • 2020 8
  • 2021 122
  • 2022 6
  • 2023 7
  • 2024 34
  • 2025 28
  • 2026 44

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

03 Vulnerabilities

Recorded vulnerabilities for ffmpeg

The 5 most severe of 692 vulnerabilities recorded for this package

Search all 692 in the database →

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 ffmpeg

Is ffmpeg safe to use?

Vulert records 692 vulnerabilities for ffmpeg in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 692 not yet rated. 58 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does ffmpeg have?

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

45 vulnerabilities were recorded for ffmpeg in the last 12 months, and the oldest entry in this database dates to 30 Nov -0001. 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 ffmpeg 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 ffmpeg for upcoming vulnerabilities?

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