CVE-2026-52295 json
FFmpeg before 9.0 has an out-of-bounds read because the copied extradata lacked required padding before GetBitContext-based access in libav…
published 2026-09-01 2 mo ago modified 2026-10-14 25 d ago also EUVD-2026-69409
- cvss
- 6.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 7%
- public exploits
- 0
- none known
Summary
FFmpeg before 9.0 has an out-of-bounds read because the copied extradata lacked required padding before GetBitContext-based access in libavformat/iamf_writer.c.
Patch / fix
- FFmpeg FFmpeg 9.0
- ffmpeg Debian 13 7:7.1.4-0+deb13u1
- ffmpeg Debian 14 7:8.1.1-1
debian advisories DEBIAN-CVE-2026-52295
- ffmpeg-8 openSUSE Tumbleweed 8.1.3-4.1
- ffmpeg-9 openSUSE Tumbleweed 9.0.2-5.1
opensuse advisories openSUSE-SU-2026:12416-1openSUSE-SU-2026:12417-1
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-52295 updated cvss 6.2
ffmpeg: FFmpeg: Denial of Service via Buffer Overflow in iamf_writer.c component
-
Red Hat Enterprise Linux AI (RHEL AI) 3 ffmpeg 6.1.6-10.el9ainot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 mo ago
Exploit prediction
0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 2.9 | CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L |
| CISA ADP | 3.1 | 6.2 | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| CNA | 3.1 | 6.2 | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected products
- FFmpeg FFmpeg
Classification
References
Sources
- CVE List CVE-2026-52295
- NVD CVE-2026-52295
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.