AI Science Tracker

FFmpeg through 9.0.2 APNG Encoder Heap Buffer Overflow via encode_apng()

FFmpeg FFmpeg · AI involvement attributed to AISLE AI-native discovery engine (model/version not disclosed)

Finding and attribution

FFmpeg through 9.0.2 contains a heap buffer overflow vulnerability in the APNG encoder's encode_apng() function in libavcodec/pngenc.c when frame size changes mid-stream. Attackers can supply crafted media whose resolution grows mid-stream, causing APNG_DISPOSE_OP_BACKGROUND memset writes past prev_frame and crashing or corrupting heap memory in transcoding applications.

Product: FFmpeg FFmpeg. AI system: AISLE AI-native discovery engine (model/version not disclosed). Team / organization: AISLE.

CVE identifiers: CVE-2026-125218.

AI and human contribution (source account): AISLE’s CVE Discoveries index lists this CVE among those its AI-native engine discovered, and the individual AISLE page says “Discovered by AISLE”. The CNA record credits “Joshua Rogers (AISLE Research); Michael Niedermayer”; a credited human name is not itself AI attribution, which rests on AISLE’s page. The model/version and the division of work between the engine and human researchers are not disclosed.

Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.

Discovery context: Public CVE disclosure is dated 2026-11-02. AISLE’s case page timeline shows 2026-11-09, used as the AI-attribution date. The cited sources establish an assigned vulnerability, not exploitation in the wild or zero-day status.

Remediation status: fix documented. Confirm the distribution-specific backport before relying on a version number.

A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.

Disclosed 2 Nov 2026. AI attribution dated 9 Nov 2026. Sources checked 17 Nov 2026; these are separate dates, not a live installation check.

Recorded CVSS: High · highest recorded score 7.3. Documented technical effects: Not available.

Severity, consequences and exploitation evidence

Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.

Technical effects, prerequisites and exploitation evidence are not established here. Missing evidence does not establish absence of exploitation.

Documented fix: Confirm the distribution-specific backport before relying on a version number.

Original evidence

Download this source record (JSON)

Open this case in the interactive tracker · Browse all static security cases