Skip to content
Applications

CVE-2026-75141

8.5
High
EPSS 0.14%Patch availableAug 20, 2026

Heap buffer overflow in FFmpeg hvcC writer allowing RCE or crash via crafted HEVC file.

common questions

Is CVE-2026-75141 being exploited?

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

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

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

What does CVE-2026-75141 affect?

CVE-2026-75141 affects FFmpeg (prior to commit acf5d7c), Applications using vulnerable FFmpeg for HEVC muxing (media servers, transcoders, players). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-75141?

Update FFmpeg to commit acf5d7c+; block or sandbox untrusted HEVC files

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

executive summary
technical analysis
affected
FFmpeg (prior to commit acf5d7c)Applications using vulnerable FFmpeg for HEVC muxing (media servers, transcoders, players)
impact

Heap overflow during HEVC muxing that can crash processes or enable remote code execution when processing untrusted HEVC inputs.

action required

Patch when possible

affected versions
FFmpeg FFmpeg
  • affected< acf5d7cdc1f9ae8752c23e1ea8d7f355ed780781

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