Skip to content
Applications

CVE-2026-65706

8.5
High
EPSS 0.13%Patch availableJul 24, 2026

Heap out-of-bounds write in FFmpeg vf_swaprect via crafted NV12 frames

common questions

Is CVE-2026-65706 being exploited?

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

How severe is CVE-2026-65706?

CVE-2026-65706 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-65706?

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

What does CVE-2026-65706 affect?

CVE-2026-65706 affects FFmpeg 3.0 through 8.1.2, Applications/services using FFmpeg vf_swaprect filter to process NV12 frames. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-65706?

Upgrade FFmpeg to a patched release or disable the vf_swaprect filter

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

executive summary
technical analysis
affected
FFmpeg 3.0 through 8.1.2Applications/services using FFmpeg vf_swaprect filter to process NV12 frames
impact

Heap corruption leading to process crash and potential remote code execution when processing malicious NV12 video frames with vf_swaprect.

action required

Patch when possible

affected versions
FFmpeg FFmpeg
  • affected>= 3.0 and <= 8.1.2
vendor says fixed ina7e38b617b32f996beaa371bbf04b39907d7a527

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