FFmpeg vulnerabilities: known CVEs & security history
FFmpeg · Media / Runtime · 6 tracked CVEs · 0 actively exploited · updated August 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all FFmpeg release lines — 6 in total. A CVE here doesn't mean your version is affected — check FFmpeg's current status and the safe version to run.
Known FFmpeg CVEs
Actively-exploited and most-severe first. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2026-64835 | high | 8.8 | 0% | 2026 |
| CVE-2026-64832 | high | 8.8 | 0% | 2026 |
| CVE-2026-64831 | high | 8.8 | 0% | 2026 |
| CVE-2026-64830 | high | 8.8 | 0% | 2026 |
| CVE-2026-64834 | high | 7.5 | 1% | 2026 |
| CVE-2026-64833 | high | 7.1 | 0% | 2026 |
Is my FFmpeg version affected?
The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.
Check your FFmpeg version → · Monitor FFmpeg for new CVEs →
FFmpeg vulnerabilities — frequently asked
How many known vulnerabilities does FFmpeg have?
IsItPatched tracks 6 CVEs for FFmpeg. 0 are critical-severity and 6 high-severity. These span every release line — what matters is whether the version you run is affected.
Does FFmpeg have any actively-exploited vulnerabilities?
None of FFmpeg's tracked CVEs are currently in CISA's KEV catalog — but new ones can be added at any time, so keep your version current.
What is the most severe FFmpeg vulnerability?
Among tracked issues, CVE-2026-64835 (HIGH, CVSS 8.8) ranks highest — a Out-of-bounds write weakness.
Is FFmpeg safe to use?
It depends on the version. The latest supported FFmpeg release (8.1.2) clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.
CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: FFmpeg security status · FFmpeg end-of-life · actively-exploited CVEs. Always verify against FFmpeg's advisories — see our disclaimer.