CVE-2026-64835
OOB read/write in FFmpeg ADX decoder via crafted mid-stream channel-change audio.
Is CVE-2026-64835 being exploited?
Not confirmed. CVE-2026-64835 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.33% probability of exploitation in the next 30 days.
How severe is CVE-2026-64835?
CVE-2026-64835 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-64835?
Yes. A fix has been recorded for CVE-2026-64835. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-64835 affect?
CVE-2026-64835 affects FFmpeg 4.4 through 8.1.2, Applications embedding vulnerable FFmpeg (media players, transcoders, streaming servers). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-64835?
Upgrade FFmpeg to a patched release; block or sanitize untrusted media files.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Malformed ADX/AAX file can trigger out-of-bounds reads/writes during decode, causing crashes or potential remote code execution in media-processing apps.
Patch when possible
- affected>= 4.4 and <= 8.1.2
- affected1836ef96846937a6cc2443698a693104f5c0b21e
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.