Skip to main content
Mallory
UnratedVulnerability

CVE-2026-39213: Heap Buffer Overflow in FFmpeg yuv4mpegenc

Updated 4 months 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-39213CWE-122

CVE-2026-39213 is a heap buffer overflow vulnerability in FFmpeg’s yuv4mpegenc component. The issue was reported as having been introduced in 2023. Available information identifies the flaw class and affected component, but does not provide the specific vulnerable function, code path, or triggering input structure. Successful exploitation would involve crafted media-processing input reaching the yuv4mpegenc encoding path and causing an out-of-bounds write on heap-allocated memory.

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.

A successful exploit can corrupt heap memory within the FFmpeg process. Depending on allocator behavior, memory layout, and execution context, this may result in process termination, denial of service, or potentially arbitrary code execution. The precise impact for this specific flaw is not further documented in the available information.

Mitigation

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

Until patched builds are deployed, reduce exposure by avoiding processing untrusted or attacker-supplied media through workflows that invoke the yuv4mpegenc path. Where operationally feasible, isolate FFmpeg in sandboxed or least-privileged execution environments, restrict access to media conversion services, and monitor for crashes or anomalous behavior during encoding operations. Mitigation details specific to this flaw are otherwise not available.

Remediation

Patch, then assume compromise.

Apply the upstream FFmpeg fix for CVE-2026-39213 or update to a vendor or distribution build that includes the corresponding security patch. Because the issue is in yuv4mpegenc and was reported as fixed upstream, remediation should prioritize upgrading FFmpeg to a release containing the patch rather than attempting ad hoc local changes.

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-39213 exploited in the wild?
As of Jul 20, 2026, Mallory has no reports of CVE-2026-39213 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-39213?
As of Jul 20, 2026, Mallory has found no public exploit for CVE-2026-39213.
Is there a patch for CVE-2026-39213?
Apply the upstream FFmpeg fix for CVE-2026-39213 or update to a vendor or distribution build that includes the corresponding security patch. Because the issue is in yuv4mpegenc and was reported as fixed upstream, remediation should prioritize upgrading FFmpeg to a release containing the patch rather than attempting ad hoc local changes.
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 activityCommunity discussion across Reddit, Mastodon, and other social sources.