CVE-2025-26667
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 · uneditedExposure of sensitive information to an unauthorized actor in Windows Routing and Remote Access Service (RRAS) 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 confidenceCVE-2025-26667 is an information disclosure vulnerability in Windows Routing and Remote Access Service (RRAS) that allows an unauthorized attacker to expose sensitive information over a network. The vulnerability stems from improper access controls within the RRAS component, potentially enabling network-adjacent attackers to retrieve sensitive data without authentication.
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 dataall versions= r2all versions= r2< 10.0.14393.7969< 10.0.17763.7136< 10.0.20348.3453< 10.0.25398.1551< 10.0.26100.3775CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Verify RRAS role is installedOn Windows Server, open Server Manager > Add Roles and Features, or run 'Get-WindowsFeature -Name RemoteAccess' in PowerShell to check if the Remote Access role (which includes RRAS) is installed.Affected if RRAS/Remote Access role is installed on the server
-
Confirm RRAS service is runningOpen Services console (services.msc) and check for 'Routing and Remote Access' service status, or run 'Get-Service RemoteAccess' in PowerShell.Affected if The RemoteAccess service is started or running
-
Check Windows Server versionRun 'winver' or execute 'Get-ComputerInfo | Select-Object OsVersion, OsBuildNumber' in PowerShell to obtain the exact build number.Affected if Build number is below 14393.7969 (Server 2016), 17763.7136 (Server 2019), 20348.3453 (Server 2022), 25398.1551 (Server 2022 23h2), or 26100.3775 (Server 2025); or if running Server 2008/2012 (any version)
-
Identify network exposure of RRASCheck RRAS configuration in Routing and Remote Access console (rrasmgmt.msc) or via 'netsh routing ip show interface' to determine which network interfaces RRAS is bound to and whether it listens on external/untrusted networks.Affected if RRAS is configured to accept connections from non-internal networks or is bound to public-facing network adapters
The environment is affected if RRAS is installed/running AND the Windows Server version falls within the unpatched build ranges specified, particularly if exposed to network access.
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.796910.0.17763.713610.0.20348.3453
Apply Microsoft security updates for Windows RRAS once available; verify RRAS is not exposed to untrusted networks and restrict access to essential personnel only.
Windows Server 2016 to build 10.0.14393.7969 | Windows Server 2019 to build 10.0.17763.7136 | Windows Server 2022 to build 10.0.20348.3453 | Windows Server 2022 23h2 to build 10.0.25398.1551 | Windows Server 2025 to build 10.0.26100.3775
- Identify the current Windows Server version by running 'winver' or 'systeminfo' in command prompt
- Determine which version range your server falls into (2016, 2019, 2022, 2022 23h2, or 2025)
- For Windows Server 2016: Upgrade to build 10.0.14393.7969 or later via Windows Update or by installing KB5055525
- For Windows Server 2019: Upgrade to build 10.0.17763.7136 or later via Windows Update or by installing KB5055493
- For Windows Server 2022: Upgrade to build 10.0.20348.3453 or later via Windows Update or by installing KB5055527
- For Windows Server 2022 23h2: Upgrade to build 10.0.25398.1551 or later via Windows Update or by installing KB5055518
- For Windows Server 2025: Upgrade to build 10.0.26100.3775 or later via Windows Update or by installing KB5055519
- After upgrade, verify the new build number matches or exceeds the fixed version for your release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26667 — 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-2025-26667 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