CVE-2026-96611

What it is

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.

At a glance

Exploitability

Can be exploited locally on the machine without logging in. High risk of data exposure, data tampering.

Exploit odds

0.1% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-09-23 15:17 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-10-15 19:43 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.1% in the next 30 days (EPSS).
• Severity: 6.9 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2026-09-23 15:17 UTC

Last modified

2026-10-15 19:43 UTC

Exploit probability

0.1% · EPSS, next 30 days

Weakness

CWE-190 · Integer overflow

Record status

Analyzed

Affected

• Ffmpeg < 9.0

Attack profile CVSS 3.1 · 6.9

Attack vector

Local

Complexity

High

Privileges needed

None

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

Low

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-96611.md and follow it. Check whether this project is affected by CVE-2026-96611. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge