dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-59208

HIGH · 7.1 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 10.0.10240.21161 / 10.0.14393.8519 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
Out-of-bounds read in Windows MapUrlToZone allows an unauthorized attacker to disclose information over a network.

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

An out-of-bounds read vulnerability exists in Windows MapUrlToZone, a function that maps URLs to security zones. The vulnerability allows an unauthorized attacker on the network to read memory beyond allocated buffers, potentially exposing sensitive information.

MitigationApply Microsoft security updates for this vulnerability through Windows Update or enterprise patch management systems. Verify that affected Windows systems receive the patch within the standard SLA window for high-severity vulnerabilities.

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.21161
Windows 10 1607Operating system
Affected:< 10.0.14393.8519
Windows 10 1809Operating system
Affected:< 10.0.17763.7919
Windows 10 21h2Operating system
Affected:< 10.0.19044.6456
Windows 10 22h2Operating system
Affected:< 10.0.19045.6456
Windows 11 22h2Operating system
Affected:< 10.0.22621.6060
Windows 11 23h2Operating system
Affected:<= 10.0.22631.6060
Windows 11 24h2Operating system
Affected:< 10.0.26100.6899

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
Low
Availability
None

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

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. Retrieve Windows version and build number
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"'. Alternatively, run 'ver' in cmd or '$PSVersionTable' in PowerShell to get the exact build number.
    Affected if The displayed build number falls below the affected version thresholds for your Windows release.
  2. Confirm Windows 10 build
    If running Windows 10, check the specific build: run 'winver' to see the version (1507, 1607, 1809, 21h2, or 22h2) and note the build number displayed.
    Affected if The build is below 10.0.10240.21161 (1507), 10.0.14393.8519 (1607), 10.0.17763.7919 (1809), 10.0.19044.6456 (21h2), or 10.0.19045.6456 (22h2).
  3. Confirm Windows 11 build
    If running Windows 11, run 'winver' to identify the feature update (22h2, 23h2, or 24h2) and note the full build number.
    Affected if The build is below 10.0.22621.6060 (22h2), or between 10.0.22631.0 and 10.0.22631.6060 inclusive (23h2), or below 10.0.26100.6899 (24h2).
  4. Verify zone mapping functionality is in use
    The MapUrlToZone function is a core Windows URL security zone mapping component. Check if Internet Explorer, Edge Legacy, or applications using URL zone parsing are present. Run 'reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\ZoneMap"' to see zone mapping configuration.
    Affected if Any Windows system with web browsing capabilities or URL processing applications installed uses this functionality; the vulnerability exists regardless of configuration.

Your system is affected if it runs any Windows 10 or 11 version with a build number lower than the thresholds listed for your specific release branch.

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.21161 / 10.0.14393.8519 / 10.0.17763.7919 or later
Fixed in 10.0.10240.2116110.0.14393.851910.0.17763.7919
Interim mitigation

Apply Microsoft security updates for this vulnerability through Windows Update or enterprise patch management systems. Verify that affected Windows systems receive the patch within the standard SLA window for high-severity vulnerabilities.

Recommended fix High confidence

Upgrade to the minimum fixed build for your Windows version: 10.0.10240.21161 (1507), 10.0.14393.8519 (1607), 10.0.17763.7919 (1809), 10.0.19044.6456 (21h2), 10.0.19045.6456 (22h2), 10.0.22621.6060 (11 22h2), >10.0.22631.6060 (11 23h2), or 10.0.26100.6899 (11 24h2)

  1. Identify the current Windows version by running 'winver' or checking System Properties
  2. Determine which Windows 10 or 11 version branch (1507, 1607, 1809, 21h2, 22h2, 23h2, or 24h2) is currently installed
  3. For Windows 10 1507: Upgrade to Windows 10 build 10.0.10240.21161 or later
  4. For Windows 10 1607: Upgrade to Windows 10 build 10.0.14393.8519 or later
  5. For Windows 10 1809: Upgrade to Windows 10 build 10.0.17763.7919 or later
  6. For Windows 10 21h2: Upgrade to Windows 10 build 10.0.19044.6456 or later
  7. For Windows 10 22h2: Upgrade to Windows 10 build 10.0.19045.6456 or later
  8. For Windows 11 22h2: Upgrade to Windows 11 build 10.0.22621.6060 or later
Caveat Standard Windows cumulative update; no breaking changes expected for this security patch

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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