CVE-2026-96611FFmpeg before 9.0 has a signed integer overflow in libavformat/mov.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 a signed integer overflow in libavformat/mov.c. In mov_read_ispe(), uint32_t width/height values from a crafted HEIF ispe box are stored into signed int fields without bounds checking, allowing values exceeding INT_MAX to become negative. In read_image_grid(), accumulating these values causes signed integer overflow (undefined behavior per C17 section 6.5), which on x86 wraps to a small positive value, bypassing downstream validity checks.
- CVSS
- 6.9 MEDIUM (v3.1, CNA)CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L
- Weakness (CWE)
- CWE-190
- 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 26, 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://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/23455issue-tracking, patch
- https://code.ffmpeg.org/FFmpeg/FFmpeg/commit/059eb2e853c1f62b8df1b73be9318061a7a21b0bpatch
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.