CVE-2026-52296: FFmpeg before 9.0 has an out-of-bounds read because of missing required padding in WMA extradata allocation pa

Q: How do I fix CVE-2026-52296?

ffmpeg: upgrade to 9.0. Exact commands for each OS are on this page.

Q: Is CVE-2026-52296 being exploited?

CVE-2026-52296 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-52296 affect?

CVE-2026-52296 affects ffmpeg. Severity is low (CVSS 2.9). FFmpeg before 9.0 has an out-of-bounds read because of missing required padding in WMA extradata allocation paths in libavcodec/wmaenc.c.

Q: How urgent is CVE-2026-52296?

Priority 11/100. No elevated risk signals yet.

Routine

LOW 2.9UPGRADE

CVE-2026-52296 is a low-severity flaw (CVSS 2.9) affecting ffmpeg. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

FFmpeg before 9.0 has an out-of-bounds read because of missing required padding in WMA extradata allocation paths in libavcodec/wmaenc.c.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	2.9 (Low)
Attack vector	Local
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	0.2% (top 95%)
CISA exploited list	No
Weakness	CWE-125
Published	2026-09-13
Last modified	2026-10-14

Publisher (CNA): MITRE · Vendor: ffmpeg

Last updated 2026-10-14 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-09-13 22:17 UTCPublished CVE record published
2026-10-14 18:24 UTCUpdated Record last modified

ffmpeg ffmpeg UPGRADE

Affected: < 9.0

Fixed in: 9.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy ffmpeg || rpm -q ffmpeg || ffmpeg --version

2. UPGRADE to 9.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade ffmpeg

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade ffmpeg

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-52296?

ffmpeg: upgrade to 9.0. Exact commands for each OS are on this page.

Is CVE-2026-52296 being exploited?

CVE-2026-52296 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-52296 affect?

CVE-2026-52296 affects ffmpeg. Severity is low (CVSS 2.9). FFmpeg before 9.0 has an out-of-bounds read because of missing required padding in WMA extradata allocation paths in libavcodec/wmaenc.c.

How urgent is CVE-2026-52296?

Priority 11/100. No elevated risk signals yet.

Software pages

FFmpeg vulnerabilities

Related CVEs

CVE-2026-64831 HIGH 8.8 UPGRADE FFmpeg versions 8.0 through 8.1.2 contains a stack buffer overflow vulnerability in the Vulkan HEVC hardware d
CVE-2026-64834 HIGH 7.5 UPGRADE FFmpeg versions 0.6.3 through 8.1.2 contain an infinite loop vulnerability in the RTP/ASF demuxer within libav
CVE-2026-64830 HIGH 8.8 UPGRADE FFmpeg versions 2.1 through 8.1.2 contains a heap buffer overflow vulnerability in the VobSub subtitle demuxer
CVE-2026-64835 HIGH 8.8 UPGRADE FFmpeg versions 4.4 through 8.1.2 contain an out-of-bounds memory access vulnerability in the ADX audio decode
CVE-2026-64832 HIGH 8.8 UPGRADE FFmpeg versions 4.4 through 8.1.2 contain a double-free vulnerability in the NVIDIA NVDEC hardware decoder wit

References

← Back to latest CVEs