CVE-2026-33825: Microsoft Defender Insufficient Granularity of Access Control
Microsoft Defender · listed in the CISA catalog of actively exploited vulnerabilities since 2026-04-22.
- CVSS v3.1 (CVE record)
- 7.8
- high
- EPSS (exploit probability, 30 days)
- 6.9%
- higher than 94.2% of all CVEs
- Added to CISA KEV
- 2026-04-22
- US federal due date 2026-05-06
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2026-33825 explained
CVE-2026-33825 is an insufficient granularity of access control flaw (CWE-1220) in Microsoft Defender on Windows. An authorized local attacker can use it to elevate privileges. CISA lists it as known exploited, including use in ransomware campaigns, so affected systems should be updated promptly.
Impact
An attacker who already has low-privileged local access can elevate privileges without user interaction. Successful exploitation gives high impact to confidentiality, integrity and availability. CISA rates the technical impact as total, meaning full control of the affected component. It is not considered automatable, so each attack needs manual steps. CISA reports active exploitation and known ransomware use.
Who is affected
The CVE record lists Microsoft Defender Antimalware Platform versions before 4.18.26030.3011 as affected. Version 4.18.26030.3011 contains the fix. Systems running an earlier platform version remain vulnerable until the platform is updated.
Written with AI from the data on this page and checked against it automatically.
Official description
Insufficient granularity of access control in Microsoft Defender allows an authorized attacker to elevate privileges locally.
CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
CISA notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- Microsoft Defender Antimalware PlatformAffectedFixed in
- < 4.18.26030.3011
- 4.18.26030.3011
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Defender Antimalware Platform |
|
|
How to fix it
- Update to a fixed version: 4.18.26030.3011.
- Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2026-33825
- CISA's deadline for US federal agencies: 2026-05-06 (passed) – a useful benchmark for everyone else, too.
What to do
- Update Microsoft Defender Antimalware Platform to
4.18.26030.3011or later on all Windows systems. - Verify the installed platform version on endpoints, especially those where automatic Defender updates may be blocked or delayed.
- Apply any mitigations in the Microsoft advisory, as CISA requires; US federal agencies must act by 2026-05-06.
- Limit local and low-privileged access to systems, and review accounts that can log on interactively.
- Check systems for signs of compromise, such as unexpected privilege changes or ransomware activity.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-1220 Insufficient Granularity of Access Control
Questions about CVE-2026-33825
- Is this vulnerability being exploited?
- Yes. CISA added CVE-2026-33825 to its Known Exploited Vulnerabilities catalog on 2026-04-22 and reports known use in ransomware campaigns.
- Can it be exploited remotely?
- No. The attack vector is local and requires an attacker who already has low-privileged access to the system. No user interaction is needed.
- Which version fixes the issue?
- Microsoft Defender Antimalware Platform
4.18.26030.3011contains the fix. Earlier versions are affected.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.