Skip to content
Applications

CVE-2026-75144

8.5
High
EPSS 0.14%Patch availableAug 20, 2026

Heap buffer overflow in FFmpeg VC-2/Dirac RTP packetizer

common questions

Is CVE-2026-75144 being exploited?

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

How severe is CVE-2026-75144?

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

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

What does CVE-2026-75144 affect?

CVE-2026-75144 affects FFmpeg <1cdeb3c, Applications using FFmpeg VC-2/Dirac RTP packetizer, Media servers/transcoders/streaming clients. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-75144?

Update FFmpeg to commit 1cdeb3c or later; rebuild and redeploy affected components

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

executive summary
technical analysis
affected
FFmpeg <1cdeb3cApplications using FFmpeg VC-2/Dirac RTP packetizerMedia servers/transcoders/streaming clients
impact

Heap buffer overflow via crafted Dirac data unit when packetized for RTP, enabling memory corruption, crashes, or potential remote code execution.

action required

Patch when possible

affected versions
FFmpeg FFmpeg
  • affected< 1cdeb3c4e7f1f8566d846b9b451e01c376398818

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