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

Code

The project this record applies to. Exploit listings stay in References.

• Repository · github.com

Timeline

Detection, updates, and resolution for this record.

1. Sep 13, 2026 · NIST NVD

   Detected

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

2. Oct 14, 2026 · NIST NVD

   Updated

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

Affected

• cpe ffmpeg/ffmpegversion unspecified

Sources

• CVE.orgVulnerability recordCVE-2026-52296

  Official CVE identifier

  cve.org
• FIRST EPSSExploitation probabilityCVE-2026-52296

  30-day exploitation probability 0.2%

  first.org
• NIST NVDVulnerability recordCVE-2026-52296

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

  nvd.nist.gov

References

• Issue Tracking · code.ffmpeg.org
• Patch · git.ffmpeg.org
• Third Party Advisory · github.com