Finding and attribution
For very large ProRes frames, 32-bit arithmetic in `ff_prores_kostya_encode_init()` could overflow while calculating the frame-size upper bound. The resulting undersized output packet allowed the encoder to write slice data beyond the allocated packet buffer.
Product: FFmpeg (ProRes `prores_ks` encoder). AI system: AISLE AI-native engine (specific model/version not disclosed). Team / organization: AISLE Research and FFmpeg maintainers.
CVE identifiers: CVE-2026-125259.
AI and human contribution (source account): AISLE’s itemized CVE index states that its listed cases were discovered by its AI-native engine and includes CVE-2026-125259. The VulnCheck CNA credits Joshua Rogers (AISLE Research) as finder, and the upstream FFmpeg fix says `Found-by: Joshua Rogers (AISLE)`. AISLE’s individual case page was unavailable in this check. The model and AI/human work split are not disclosed; no priority claim is made.
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 CNA record gives a public disclosure date of October 29, 2026; it was published with finder credit on November 9, 2026, the date AISLE’s itemized index places this case in its AI-native-engine-discovered list. The upstream fix reproduces signed overflow under UBSAN and an out-of-array write under ASAN. The vulnerable path requires using the ProRes encoder on sufficiently large frame dimensions; no remote exploitation claim is made.
Remediation status: fix documented. FFmpeg commit 439b452f9fe916a9f7d8788ab6afee8fac846b0b computes the frame-size upper bound in 64 bits, checks that size against `INT_MAX`, and derives the slice upper bound safely. Downstream package release status varies and is not asserted here.
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 29 Oct 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: other.
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-125259: 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-125259: 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-125259: other.
Prerequisites / affected scope: FFmpeg through 9.0.2 contains an integer overflow vulnerability in ff_prores_kostya_encode_init() that miscalculates frame_size_upper_bound using 32-bit arithmetic for large frame dimensions. Attackers can supply a high-resolution video transcoded with the prores_ks encoder, causing encode_frame() to write slices past an undersized packet buffer and corrupt heap memory. Integer Overflow or Wraparound.
Exploitation evidence: The cited source does not state whether this issue was exploited in the wild.. Impact source · checked 16 Nov 2026.
Documented fix: FFmpeg commit 439b452f9fe916a9f7d8788ab6afee8fac846b0b computes the frame-size upper bound in 64 bits, checks that size against `INT_MAX`, and derives the slice upper bound safely. Downstream package release status varies and is not asserted here.