Skip to main content
Mallory
UnratedVulnerability

CVE-2026-39211: Integer Overflow in FFmpeg swscale

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-39211CWE-190

CVE-2026-39211 is an integer overflow vulnerability in FFmpeg's swscale component. The issue was reportedly introduced in 2010. The available information identifies the flaw class and affected subsystem, but does not provide the specific vulnerable function, code path, trigger condition, or memory-safety consequences beyond the presence of an integer overflow. swscale is used for image scaling and pixel format conversion, so malformed or attacker-controlled media inputs that reach this processing path could potentially trigger incorrect size or arithmetic calculations during scaling operations.

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.

Successful exploitation may allow memory corruption, process instability, or denial of service in applications that invoke the vulnerable swscale code path on attacker-controlled media content. Because the available information only identifies the issue as an integer overflow and does not document the exact downstream effect, the precise impact beyond erroneous arithmetic and potential unsafe memory handling is currently not available.

Mitigation

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

Until patches can be applied, reduce exposure by limiting or isolating workflows that process untrusted media through FFmpeg scaling or pixel-conversion paths. Prefer sandboxing FFmpeg-based processing, restricting accepted media sources and formats where operationally feasible, and separating media transformation services from sensitive systems. Because the exact trigger conditions are not available, mitigation can only be generalized to minimizing attacker-controlled input to swscale.

Remediation

Patch, then assume compromise.

Update FFmpeg to a version containing the upstream fix for CVE-2026-39211, or apply the corresponding vendor or distribution security update that incorporates the patched swscale code. If FFmpeg is statically bundled into downstream products, rebuild and redeploy those applications against a fixed FFmpeg release.

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-39211 exploited in the wild?
As of Jul 20, 2026, Mallory has no reports of CVE-2026-39211 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-39211?
As of Jul 20, 2026, Mallory has found no public exploit for CVE-2026-39211.
Is there a patch for CVE-2026-39211?
Update FFmpeg to a version containing the upstream fix for CVE-2026-39211, or apply the corresponding vendor or distribution security update that incorporates the patched swscale code. If FFmpeg is statically bundled into downstream products, rebuild and redeploy those applications against a fixed FFmpeg release.
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.