dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-27737

HIGH · 8.6 CVSS v3.1 Published 2025-04-08
Fix available
A fix is available. Upgrade to 10.0.10240.20978 / 10.0.14393.7969 or later.
See remediation →
89/100
Remediation priority · High
No privileges

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
Improper input validation in Windows Security Zone Mapping allows an unauthorized attacker to bypass a security feature locally.

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

Improper input validation in Windows Security Zone Mapping allows a local unauthorized attacker to bypass a security feature by manipulating how URLs or content are mapped to security zones, potentially elevating privileges or bypassing security restrictions.

MitigationApply the relevant Windows security update from Microsoft's monthly patch cycle to fix the input validation vulnerability in Security Zone Mapping.

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:< 10.0.10240.20978
Windows 10 1607Operating system
Affected:< 10.0.14393.7969
Windows 10 1809Operating system
Affected:< 10.0.17763.7136
Windows 10 21h2Operating system
Affected:< 10.0.19044.5737
Windows 10 22h2Operating system
Affected:< 10.0.19045.5737
Windows 11 22h2Operating system
Affected:< 10.0.22621.5189
Windows 11 23h2Operating system
Affected:< 10.0.22631.5189
Windows 11 24h2Operating system
Affected:< 10.0.26100.3775

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/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. Check Windows build version
    Open Command Prompt or PowerShell and run: winver.exe or run: systeminfo | findstr /B /C:"OS Name" /C:"OS Version"
    Affected if The build number is lower than the affected version for your Windows release (1507: <10240.20978, 1607: <14393.7969, 1809: <17763.7136, 21h2: <19044.5737, 22h2: <19045.5737, 11 22h2: <22621.5189, 11 23h2: <22631.5189, 11 24h2: <26100.3775)
  2. Confirm Windows 10 release
    Run in PowerShell: [System.Environment]::OSVersion.Version or run: winver to see the specific Windows 10 release name (1507, 1607, 1809, 21h2, or 22h2)
    Affected if The detected release matches one of the affected Windows 10 versions listed and the build is below the corresponding threshold
  3. Confirm Windows 11 release
    Run in PowerShell: Get-ComputerInfo | Select WindowsVersion,OsDisplayVersion or check via winver to identify 22h2, 23h2, or 24h2
    Affected if The detected Windows 11 release matches 22h2, 23h2, or 24h2 and the build is below the corresponding threshold for that release

You are affected if your Windows version build number falls below the threshold for your specific Windows release (10 or 11, including the specific sub-version like 22h2 or 23h2) as listed in the affected versions.

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
Upgrade available Upgrade to 10.0.10240.20978 / 10.0.14393.7969 / 10.0.17763.7136 or later
Fixed in 10.0.10240.2097810.0.14393.796910.0.17763.7136
Interim mitigation

Apply the relevant Windows security update from Microsoft's monthly patch cycle to fix the input validation vulnerability in Security Zone Mapping.

Recommended fix High confidence

Apply the May 2025 (or later) Windows security update. For each affected version, the minimum fixed builds are: Windows 10 1507: 10.0.10240.20978, Windows 10 1607: 10.0.14393.7969, Windows 10 1809: 10.0.17763.7136, Windows 10 21h2: 10.0.19044.5737, Windows 10 22h2: 10.0.19045.5737, Windows 11 22h2:

  1. Identify the current Windows version and build number by running 'winver' or 'systeminfo'
  2. Determine which Windows 10 or 11 version and build you are running
  3. Apply the appropriate Microsoft security update for CVE-2025-27737. This is addressed in the May 2025 Windows security updates.
  4. Verify the update was installed successfully by checking Windows Update history or running 'winver' to confirm the build number matches or exceeds the fixed version for your release channel
  5. Restart the system if prompted to complete the installation
Caveat Standard Windows security update with no expected breaking changes; as with any system update, test critical applications after deployment in production environments

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,360
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-27737 — 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-2025-27737 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