Skip to main content
Mallory
HighVulnerability

CVE-2026-113749: Remote Code Execution in Microsoft Windows Codecs Library

Published Nov 10, 2026 · Updated 6 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days6 mentions · peak 3 in a dayToday
CVSS7.5High · v3.1
EPSS0.79%57th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Microsoft Corporation
IdentifiersCVE-2026-113749CWE-122 · Heap-based Buffer Overflow

CVE-2026-113749 is a heap-based buffer overflow in Microsoft Windows Codecs Library that permits unauthenticated remote code execution when a user opens, previews, or otherwise processes specially crafted media. An integer overflow or wraparound can cause an undersized heap allocation, followed by an out-of-bounds write during decoding. Successful exploitation executes attacker-controlled code in the decoding process's security context. The vulnerability affects Windows client and server releases. Microsoft rates it Critical with a CVSS v3.1 base score of 7.5; exploitation requires user interaction and high attack complexity.

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 can compromise confidentiality, integrity, and availability within the affected process's security context. Potential consequences include data theft, modification or destruction of accessible data, credential harvesting, malware deployment, and disruption of the affected application. Broader compromise depends on the decoding process's privileges and access; SYSTEM-level execution is not established.

Mitigation

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

No official workaround is identified. Until updates are installed, block or quarantine untrusted media attachments at email and web gateways, discourage users from opening or previewing unexpected media, and limit user and application privileges to reduce exploitation impact. These precautions do not replace patching.

Remediation

Patch, then assume compromise.

Apply the applicable Microsoft security update addressing CVE-2026-113749, using Microsoft's per-CVE update guidance to select the package for the installed Windows release and architecture. An official fix is available, but specific update identifiers and fixed builds are not available here. Prioritize workstations where users routinely open media files, followed by servers that process untrusted media.

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.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationWindows 10 1607operating_system
Microsoft CorporationWindows 10 1809operating_system
Microsoft CorporationWindows 10 21h2operating_system
Microsoft CorporationWindows 10 22h2operating_system
Microsoft CorporationWindows 11 23h2operating_system
Microsoft CorporationWindows 11 24h2operating_system
Microsoft CorporationWindows 11 25h2operating_system
Microsoft CorporationWindows 11 26h1operating_system
Microsoft CorporationWindows 11 Version 26H2 For Arm64-Based Systemsapplication
Microsoft CorporationWindows Server 2016operating_system
Microsoft CorporationWindows Server 2019operating_system
Microsoft CorporationWindows Server 2022operating_system
Microsoft CorporationWindows Server 2025operating_system
FAQ

Frequently asked questions

Is CVE-2026-113749 exploited in the wild?
As of Nov 12, 2026, Mallory has no reports of CVE-2026-113749 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-113749?
As of Nov 12, 2026, Mallory has found no public exploit for CVE-2026-113749.
Is there a patch for CVE-2026-113749?
Apply the applicable Microsoft security update addressing CVE-2026-113749, using Microsoft's per-CVE update guidance to select the package for the installed Windows release and architecture. An official fix is available, but specific update identifiers and fixed builds are not available here.
What products are affected by CVE-2026-113749?
Microsoft Corporation Windows 10 1607, Microsoft Corporation Windows 10 1809, Microsoft Corporation Windows 10 21h2, Microsoft Corporation Windows 10 22h2, Microsoft Corporation Windows 11 23h2, and 8 more.
How severe is CVE-2026-113749?
CVE-2026-113749 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 0.79% (57th percentile) as of Nov 12, 2026.
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.