Skip to main content
Mallory
UnratedVulnerability

CVE-2026-39210: Heap buffer overflow in FFmpeg TS demuxer

Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-39210CWE-122

CVE-2026-39210 is a heap buffer overflow in FFmpeg's transport stream (TS) demuxer. The flaw was introduced in 2010 and is among the FFmpeg vulnerabilities discovered by DepthFirst and addressed through upstream fixes. The specific vulnerable function, triggering input, and affected release range are not available.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

The vulnerability involves heap memory corruption in FFmpeg's TS demuxer. Whether exploitation can cause a process crash, disclose information, or execute arbitrary code is not established by the available vulnerability-specific information.

Mitigation

If you can’t patch tonight, do this now.

Until patched builds are fully deployed, reduce exposure by preventing untrusted or externally supplied MPEG transport stream content from reaching vulnerable FFmpeg processing paths. Disable or isolate workflows that automatically demux attacker-controlled TS media where operationally feasible. Run FFmpeg-based services with least privilege, strong sandboxing, and process isolation to limit post-exploitation impact. Additional hardening such as ASLR, modern heap protections, and container or seccomp confinement may reduce exploit reliability but do not eliminate the underlying flaw.

Remediation

Patch, then assume compromise.

Update FFmpeg to an upstream build or distribution security update containing the fix for CVE-2026-39210. A specific fixed release or patch identifier is not available.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-39210 exploited in the wild?
As of Oct 12, 2026, Mallory has no reports of CVE-2026-39210 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-39210?
As of Oct 12, 2026, Mallory has found no public exploit for CVE-2026-39210.
Is there a patch for CVE-2026-39210?
Update FFmpeg to an upstream build or distribution security update containing the fix for CVE-2026-39210. A specific fixed release or patch identifier is not available.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity6Community discussion across Reddit, Mastodon, and other social sources.