dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-25173

HIGH · 8.0 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 10.0.14393.8957 / 10.0.17763.8511 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable

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
Integer overflow or wraparound in Windows Routing and Remote Access Service (RRAS) allows an authorized attacker to execute code 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 integer overflow or wraparound vulnerability exists in Windows Routing and Remote Access Service (RRAS) that allows an authenticated attacker to execute arbitrary code over a network. The vulnerability stems from improper input validation in RRAS handling of network requests.

MitigationApply Microsoft security patches when released; until then, restrict network access to RRAS servers, enforce least privilege access, and consider network segmentation to limit exposure.

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 1607Operating system
Affected:< 10.0.14393.8957
Windows 10 1809Operating system
Affected:< 10.0.17763.8511
Windows 10 21h2Operating system
Affected:< 10.0.19044.7058
Windows 10 22h2Operating system
Affected:< 10.0.19045.7058
Windows 11 23h2Operating system
Affected:< 10.0.22631.6783
Windows 11 24h2Operating system
Affected:< 10.0.26100.7979
Windows 11 25h2Operating system
Affected:< 10.0.26200.7979
Windows 11 26h1Operating system
Affected:< 10.0.28000.1719

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
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Verify RRAS is installed
    Open Server Manager > Add Roles and Features, or run 'Get-WindowsFeature -Name Routing' in PowerShell on Windows Server. On Windows client, check 'Programs and Features > Turn Windows features on or off' for 'Routing and Remote Access' (RRAS).
    Affected if RRAS role/service is installed and enabled on the system
  2. Check Windows build version
    Run 'winver' from command prompt, or 'Get-ComputerInfo | Select-Object OsVersion, OsBuildNumber' in PowerShell, or check System Properties.
    Affected if Build number falls below the affected thresholds (14393.8957, 17763.8511, 19044.7058, 19045.7058, 22631.6783, 26100.7979, 26200.7979, or 28000.1719 depending on Windows version)
  3. Confirm RRAS is running
    Run 'Get-Service RemoteAccess' in PowerShell, or check Services console for 'Routing and Remote Access' service status.
    Affected if The RemoteAccess service is in a Running state and RRAS is actively handling network requests

System is affected if RRAS is installed/enabled AND the Windows build version is below the threshold for that specific Windows release.

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.14393.8957 / 10.0.17763.8511 / 10.0.19044.7058 or later
Fixed in 10.0.14393.895710.0.17763.851110.0.19044.7058
Interim mitigation

Apply Microsoft security patches when released; until then, restrict network access to RRAS servers, enforce least privilege access, and consider network segmentation to limit exposure.

Recommended fix High confidence

Upgrade to the version number at or above the threshold for your Windows version (e.g., Windows 10 1607 to 10.0.14393.8957 or later, Windows 11 23h2 to 10.0.22631.6783 or later)

  1. Identify the current Windows version by running 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"'
  2. Navigate to Settings > Windows Update and check for available updates
  3. Install all pending Windows updates, particularly cumulative security updates
  4. Alternatively, manually download and install the specific security update for this CVE from the Microsoft Update Catalog (search for the CVE number)
  5. After installation, restart the system to apply the updates
  6. Verify the update was successful by checking the Windows version matches or exceeds: 10.0.14393.8957 (Win10 1607), 10.0.17763.8511 (Win10 1809), 10.0.19044.7058 (Win10 21h2), 10.0.19045.7058 (Win10 22h2), 10.0.22631.6783 (Win11 23h2), 10.0.26100.7979 (Win11 24h2), 10.0.26200.7979 (Win11 25h2), or 10.0.28000.1719 (Win11 26h1)
Caveat Standard Windows cumulative updates; verify critical applications are compatible before deploying in production environments

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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