Skip to main content

Microsoft Defender CVE-2026-55011

| EUVDEUVD-2026-44029 HIGH
Integer Underflow (CWE-191)
2026-07-14 microsoft GHSA-9gvv-f74q-gxrr
7.8
CVSS 3.1 · Vendor: microsoft
Share

Severity by source

Vendor (microsoft) PRIMARY
7.8 HIGH
AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
vuln.today AI
7.8 HIGH

Local file must be scanned by the engine (AV:L, UI:R), no privileges needed (PR:N), and SYSTEM-level engine execution yields full C:H/I:H/A:H.

3.1 AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

Attack Vector
Local
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Analysis Generated
Jul 14, 2026 - 17:58 vuln.today
CVE Published
Jul 14, 2026 - 17:05 nvd
HIGH 7.8

DescriptionCVE.org

Integer underflow (wrap or wraparound) in Microsoft Defender allows an unauthorized attacker to execute code locally.

AnalysisAI

Local code execution in Microsoft Defender's Malware Protection Engine (mpengine) arises from an integer underflow (CWE-191) that a local attacker can trigger with no prior authentication but requiring user interaction, yielding high confidentiality, integrity, and availability impact. Because Defender's scanning engine runs with SYSTEM-level privileges, successful exploitation would grant full compromise of the host. There is no public exploit identified at time of analysis and the issue is not listed in CISA KEV; Microsoft has released a fix.

Technical ContextAI

The affected component is the Microsoft Malware Protection Engine (mpengine.dll), the shared scanning core behind Microsoft Defender Antivirus, Security Essentials, and related endpoint products. The root cause is CWE-191 (integer underflow/wraparound): an arithmetic operation subtracts past zero and wraps to a very large unsigned value, which typically leads to undersized buffer allocations or out-of-bounds reads/writes when the engine parses attacker-influenced content. Antimalware engines are historically high-value targets because they automatically and often eagerly parse untrusted file formats (archives, executables, scripts) at maximum privilege, so a parsing arithmetic error translates directly into memory-corruption-grade impact. The single CPE provided (cpe:2.3:a:microsoft:microsoft_malware_protection_engine) confirms the engine itself, rather than a specific Defender UI or platform build, is the vulnerable unit.

RemediationAI

Patch available per vendor advisory: ensure the Microsoft Malware Protection Engine updates to the fixed build referenced at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-55011. In most environments no manual action is required because the engine auto-updates alongside security intelligence definitions, typically within 48 hours; verify by confirming the engine version in Windows Security under 'About' (or via Get-MpComputerStatus reporting AMEngineVersion) matches or exceeds the version cited in the advisory. For managed or air-gapped fleets that disable automatic engine updates, manually push the updated engine through WSUS, Microsoft Configuration Manager, or the standalone definition package. As an interim compensating control where updating is delayed, reduce untrusted-file exposure to the scanner - for example restrict inbound file transfer paths and email attachment delivery - but note this does not remove the vulnerability and degrades protection, so it should only bridge the short gap before the engine update lands.

Share

CVE-2026-55011 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy