CVE-2026-23674
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 · uneditedImproper resolution of path equivalence in Windows MapUrlToZone allows an unauthorized attacker to bypass a security feature 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 confidenceImproper path equivalence resolution in Windows MapUrlToZone allows attackers to bypass security zone restrictions by using crafted URL path variations that are incorrectly parsed, potentially allowing malicious content to be treated as if it originated from a trusted zone.
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< 10.0.14393.8957< 10.0.17763.8511< 10.0.19044.7058< 10.0.19045.7058< 10.0.22631.6783< 10.0.26100.7979< 10.0.26200.7979< 10.0.28000.1719CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check Windows version using winverOpen Command Prompt and run `winver` to display the Windows version and build numberAffected if The displayed version/build is lower than any of the affected ranges (10.0.14393.8957, 10.0.17763.8511, 10.0.19044.7058, 10.0.19045.7058, 10.0.22631.6783, 10.0.26100.7979, 10.0.26200.7979, or 10.0.28000.1719)
-
Check detailed build information via systeminfoRun `systeminfo` in Command Prompt and locate the OS Name and OS Version fieldsAffected if The build number shown is less than the fixed build for your Windows release branch
-
Identify Windows release branchDetermine if you are on Windows 10 1607, 1809, 21h2, 22h2, or Windows 11 23h2, 24h2, 25h2, or 26h1 by checking the OS name in systeminfoAffected if Your specific release branch build is below the corresponding threshold listed in the affected versions
-
Confirm MapUrlToZone component presenceThe vulnerability exists in the MapUrlToZone URL parsing component; this is a Windows internal DLL used by Internet Explorer and Edge for security zone mapping - no direct file check is feasible but the version check above confirms exposureAffected if Your Windows version is in the affected range and you use browsers or applications that rely on Windows security zone URL parsing
You are affected if your Windows version build number is lower than the threshold for your specific Windows release branch shown in the affected versions list.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.0.14393.895710.0.17763.851110.0.19044.7058
Apply Microsoft security updates for Windows when available; until then, restrict network access to affected systems and monitor for unusual URL patterns in requests.
Windows 10 1607: build 10.0.14393.8957 or later | Windows 10 1809: build 10.0.17763.8511 or later | Windows 10 21h2: build 10.0.19044.7058 or later | Windows 10 22h2: build 10.0.19045.7058 or later | Windows 11 23h2: build 10.0.22631.6783 or later | Windows 11 24h2: build 10.0.26100.7979 or later |
- Open Windows Settings and navigate to Windows Update
- Check for and install all pending Windows updates, or manually trigger a check for updates
- Verify the installed Windows build number matches or exceeds the fixed version for your Windows edition: Windows 10 1607 should be 10.0.14393.8957 or later, Windows 10 1809 should be 10.0.17763.8511 or later, Windows 10 21h2 should be 10.0.19044.7058 or later, Windows 10 22h2 should be 10.0.19045.7058 or later, Windows 11 23h2 should be 10.0.22631.6783 or later, Windows 11 24h2 should be 10.0.2610
- Alternatively, download and install the specific Windows security update from the Microsoft Update Catalog for your Windows version and architecture
- Restart the system after applying the update
- Confirm the vulnerability is resolved by verifying the installed build number matches or exceeds the fixed version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2026-23674 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-23674 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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