Finding and attribution
The APAC decoder can retain a stale `bitstream_index` across packets. With a sufficiently large bitstream, integer overflow can bypass the allocation/reallocation check and lead to an out-of-bounds heap write or crash while decoding a crafted APAC file.
Product: FFmpeg (APAC audio decoder). AI system: AISLE AI-native engine (specific model/version not disclosed). Team / organization: AISLE Research and FFmpeg contributors.
CVE identifiers: CVE-2026-125267.
AI and human contribution (source account): AISLE’s itemized AI-discovery index explicitly lists this CVE under the statement that its AI-native engine discovered the listed cases. However, the official CVE record credits Umar Pathan as finder and Joshua Rogers (AISLE Research) as reporter; the upstream fix is authored and found by Umar Pathan. I preserve this source-credit mismatch, do not infer the human finder was AI or unassisted, and make no priority claim. The AI model/work split is 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: The CVE Program record gives September 9, 2026 as `datePublic`, while the public CVE record and AISLE AI-index attribution appeared November 9. The APAC decoder is affected before FFmpeg 8.1.3 and in 9.0 before 9.0.2; the upstream patch resets the index unconditionally. Crafted audio must be decoded; no in-the-wild exploitation is established.
Remediation status: fix documented. FFmpeg commit e15ddb7f9a2f9b3ab8ac305efb6f94ddc18463d0 resets `bitstream_index` unconditionally and fixes the APAC heap out-of-bounds write. CVE data lists FFmpeg before 8.1.3 and 9.x before 9.0.2 as affected; downstream package deployment varies.
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 9 Sep 2026. AI attribution dated 9 Nov 2026. Sources checked 15 Nov 2026; these are separate dates, not a live installation check.
Recorded CVSS: High · highest recorded score 8.5. Documented technical effects: denial of service.
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.
- CVE-2026-125267: CVSS 4.0 · 8.5 (High) ·
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N. VulnCheck (CNA; CVE Program record) · checked 16 Nov 2026. - CVE-2026-125267: CVSS 3.1 · 7.8 (High) ·
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. VulnCheck (CNA; CVE Program record) · checked 16 Nov 2026.
CVE-2026-125267: denial of service.
Prerequisites / affected scope: The CNA description states: FFmpeg before 8.1.3 and 9.x before 9.0.2 contains a heap out-of-bounds write vulnerability in the APAC decoder in libavcodec/apac.c caused by an unreset bitstream index. Attackers can supply a crafted APAC file whose growing bitstream_index triggers an integer overflow, bypassing the reallocation check so memcpy() corrupts heap memory or crashes the application..
Exploitation evidence: Exploitation in the wild is not established by the cited description.. Impact source · checked 16 Nov 2026.
Documented fix: FFmpeg commit e15ddb7f9a2f9b3ab8ac305efb6f94ddc18463d0 resets `bitstream_index` unconditionally and fixes the APAC heap out-of-bounds write. CVE data lists FFmpeg before 8.1.3 and 9.x before 9.0.2 as affected; downstream package deployment varies.