Skip to content
Applications

CVE-2026-75142

8.5
High
EPSS 0.14%Patch availableAug 20, 2026

Stack buffer overflow in FFmpeg MPEG-PS muxer permitting crash or RCE via crafted input

common questions

Is CVE-2026-75142 being exploited?

Not confirmed. CVE-2026-75142 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-75142?

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

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

What does CVE-2026-75142 affect?

CVE-2026-75142 affects FFmpeg (pre-commit 9d786e4), Applications/libraries embedding FFmpeg MPEG-PS muxer, Media servers, transcoders, streaming platforms. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-75142?

Upgrade FFmpeg to commit 9d786e4+ and avoid processing untrusted MPEG-PS inputs

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

executive summary
technical analysis
affected
FFmpeg (pre-commit 9d786e4)Applications/libraries embedding FFmpeg MPEG-PS muxerMedia servers, transcoders, streaming platforms
impact

Crafted MPEG-PS input with excessive streams can trigger a stack buffer overflow, causing process crash or potential remote code execution in the muxing process.

action required

Immediate action required

affected versions
FFmpeg FFmpeg
  • affected< 9d786e4b5e9b8482651928574de33772aeee7be1

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