CVE-2026-52296FFmpeg before 9.0 has an out-of-bounds read because of missing required padding in WMA extradata allocation paths in libavcodec/wmaenc.c.
Updated under an hour ago ()
Does this affect you?
It affects FFmpeg. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
FFmpeg before 9.0 has an out-of-bounds read because of missing required padding in WMA extradata allocation paths in libavcodec/wmaenc.c.
- CVSS
- 2.9 LOW (v3.1, CNA)CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
- Weakness (CWE)
- CWE-125
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- mitre
- NVD analysis
- Analyzed
- Record last updated
- Sep 15, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
FFmpeg FFmpeg ffmpeg:ffmpeg (from the name) | before 9.0 | CNA record |
ffmpeg ffmpeg ffmpeg:ffmpeg | before 9.0 | NVD |
References
- https://github.com/Kenan-Kamel/VulnerabilitiesReference/tree/main/FFmpeg/ExtradataPaddingthird-party-advisory
- https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/22988issue-tracking, patch
- https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/23227a444de4a8f7696f46660cdd044b460f7e47patch
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.