Skip to content
Applications

CVE-2026-65703

8.5
High
EPSS 0.19%Patch availableJul 24, 2026

Out-of-bounds write in FFmpeg TDSC decoder via crafted AVI leading to crash or RCE

common questions

Is CVE-2026-65703 being exploited?

Not confirmed. CVE-2026-65703 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.19% probability of exploitation in the next 30 days.

How severe is CVE-2026-65703?

CVE-2026-65703 is rated High with a CVSS score of 8.5. 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-65703?

Yes. A fix has been recorded for CVE-2026-65703. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-65703 affect?

CVE-2026-65703 affects FFmpeg 2.7 through 8.1.2, Any application embedding vulnerable FFmpeg builds, Media players/servers using TDSC decoder. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-65703?

Update to vendor-fixed FFmpeg or disable TDSC decoder; block/unpack untrusted AVI files.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
FFmpeg 2.7 through 8.1.2Any application embedding vulnerable FFmpeg buildsMedia players/servers using TDSC decoder
impact

Heap out-of-bounds write when parsing crafted AVI TDSF frames, causing process crash and potential remote code execution.

action required

Patch when possible

affected versions
FFmpeg FFmpeg
  • affected>= 2.7 and <= 8.1.2
vendor says fixed infd3ee52fab34d98a95b787d0b5ff45685766200c

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free