What is CVE-2026-33825?
Insufficient granularity of access control in Microsoft Defender allows an authorized attacker to elevate privileges locally.
Timeline
- 2026-04-14Published to the U.S. National Vulnerability Database (NVD)
- 2026-04-22Added to the CISA Known Exploited Vulnerabilities (KEV) catalog
- 2026-05-06CISA federal remediation deadline (set under BOD 22-01, since superseded by BOD 26-04)
- 2026-07-01First covered in a defend.network daily briefing
- 2026-07-24NVD record last updated
CISA Known Exploited Vulnerability
Microsoft Defender Insufficient Granularity of Access Control Vulnerability
Affected product
Microsoft Defender
Remediation Steps
- Apply the vendor security update for Microsoft Defender as a priority.
- Restrict network exposure of the affected service to trusted sources until patched.
- Review logs and detections for indicators of exploitation.
- Confirm fixed versions against the official vendor advisory before deploying.
References
- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-33825
- https://www.huntress.com/blog/nightmare-eclipse-intrusion
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-33825
- https://nvd.nist.gov/vuln/detail/CVE-2026-33825
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog
Referenced in our briefings & reports
- Vulnerability Priority Report – Week 5 of June 2026 (June 29 – July 5)
- AI agent poisoning, Langflow RCE exploited: Microsoft warns data theft risks (2026-07-01)
Related vulnerabilities
- CVE-2026-41091 – Microsoft Defender (same product)
- CVE-2026-56155 – Microsoft Active Directory Federation Services (same vendor)
- CVE-2026-124194 – Microsoft Office (same vendor)
- CVE-2026-96951 – Microsoft Windows (same vendor)
- CVE-2026-85889 – Microsoft Azure Ai Foundry (same vendor)
- CVE-2026-69730 – Microsoft Windows (same vendor)
Browse all tracked CVEs in the defend.network CVE database →
🤖 This CVE page is generated by defend.network from NVD, CISA KEV, EPSS, and our verified daily briefings. Severity and exploitation data come from official sources; always verify remediation steps against the official vendor advisory before acting in production.