CVE-2023-36025
Published: November 14, 2023
Official Description
Microsoft Windows SmartScreen contains a security feature bypass vulnerability that could allow an attacker to bypass Windows Defender SmartScreen checks and their associated prompts.
CISA KEV Advisory
Microsoft Windows SmartScreen Security Feature Bypass Vulnerability
Microsoft Windows SmartScreen contains a security feature bypass vulnerability that could allow an attacker to bypass Windows Defender SmartScreen checks and their associated prompts.
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Risk Analysis
This Microsoft Windows SmartScreen vulnerability allows attackers to bypass security checks, potentially leading to the execution of malicious content without user prompts. Its high EPSS score of 0.90206 and inclusion in CISA's KEV underscore the urgency of patching this actively exploited flaw.
This vulnerability is actively exploited in the wild, as confirmed by its presence in CISA's Known Exploited Vulnerabilities catalog.
Apply the latest security updates from Microsoft to address the Windows SmartScreen bypass. Ensure Windows Defender SmartScreen is enabled and configured correctly.
Technical Analysis
CVE-2023-36025 requires local access, meaning attackers must already have a foothold on the target system.
Exploitation requires some privileges, which limits the exposure to scenarios where an attacker has already gained initial access.
CISA has added CVE-2023-36025 to the Known Exploited Vulnerabilities (KEV) catalog, confirming active exploitation in the wild. U.S. federal agencies are required to patch this within the mandated timeframe, and all organizations should treat remediation as urgent.
Affected Vendors & Products
Exploit & PoC Resources
All References (2)
Quick Facts
Recommended Actions
- →Apply vendor patches immediately
- →Monitor CVE-2023-36025 in threat intel feeds
- →Review IDS/IPS signatures for exploitation attempts
- !CISA KEV: Federal agencies must patch per BOD 22-01 timeline
- !Active exploitation confirmed — treat as P1