dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 5 Dec 2023.
Windows 10 1507Operating system · Microsoft

CVE-2023-36025

HIGH · 8.8 CVSS v3.1 Published 2023-11-14
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Remotely reachable No privileges Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Windows SmartScreen Security Feature Bypass Vulnerability

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a security feature bypass vulnerability in Windows SmartScreen, which is a built-in Windows security feature that warns users before running potentially malicious files downloaded from the internet. The vulnerability allows attackers to circumvent this protection mechanism, potentially enabling the execution of malicious files that would otherwise be blocked.

MitigationApply the Microsoft security update (KB5032288 or subsequent relevant patches) to affected Windows systems to remediate this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows 10 1507Operating system
Affected:all versions
Windows 10 1607Operating system
Affected:all versions
Windows 10 1809Operating system
Affected:all versions
Windows 10 21h2Operating system
Affected:all versions
Windows 10 22h2Operating system
Affected:all versions
Windows 11 21h2Operating system
Affected:all versions
Windows 11 22h2Operating system
Affected:all versions
Windows 11 23h2Operating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Windows version is affected
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' and identify the exact Windows build and version (e.g., 10.0.19044 for Windows 10 21h2, 10.0.22000 for Windows 11 21h2, 10.0.22621 for Windows 11 22h2, 10.0.22631 for Windows 11 23h2). Compare against the affected versions listed: Windows 10 1507, 1607, 1809, 21h2, 22h2 and Windows 11 21h2, 22h2, 23h2.
    Affected if The system runs any of the affected Windows 10 or Windows 11 versions listed in the CVE
  2. Verify SmartScreen protection is enabled
    Open Windows Security > App & browser control > Reputation-based protection, or run 'Get-MpComputerStatus' in PowerShell and check the 'SmartScreenEnabled' field. Alternatively, check registry key 'HKLM\SOFTWARE\Policies\Microsoft\Windows\System\EnableSmartScreen' (value should be 1 if enabled).
    Affected if SmartScreen is enabled (the bypass only matters if the protection is actually active)
  3. Check if security update is installed
    Open Settings > Windows Update > View update history, or run 'wmic qfe list' in Command Prompt, and look for the December 2023 cumulative security update (KB5032xxx series depending on Windows version). Alternatively, check registry 'HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages' for installed security patch packages.
    Affected if The December 2023 security update for CVE-2023-36025 is NOT installed - the system remains vulnerable

You are affected if you run an affected Windows 10/11 version, SmartScreen is enabled, and the December 2023 security update (KB5032xxx) has not been installed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch msrc.microsoft.com →
Interim mitigation

Apply the Microsoft security update (KB5032288 or subsequent relevant patches) to affected Windows systems to remediate this vulnerability.

Recommended fix Moderate confidence
  1. Apply the Microsoft security update for CVE-2023-36025. This vulnerability was addressed in the November 2023 security updates. Contact your IT department or system administrator to ensure Windows Update is enabled and that pending security updates are installed.
  2. Verify the patch has been applied by checking Windows Update history for the November 2023 security update installation.
  3. For enterprise environments, verify through your patch management solution that the appropriate Microsoft security bulletin (likely CVE-2023-36025) has been deployed to all affected systems.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1507 Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-36025 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-36025 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data