CVE-2025-26676
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 · uneditedBuffer over-read 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 confidenceThis is a buffer over-read vulnerability in Windows Routing and Remote Access Service (RRAS). An unauthenticated attacker on the network can exploit this to read memory beyond allocated buffers, potentially exposing sensitive information from the RRAS process.
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 installationRun PowerShell command: Get-WindowsFeature -Name RemoteAccess | Select-Object -Property Name,Installed. On client Windows, check Programs and Features for 'Routing and Remote Access' or check services list.Affected if RRAS is installed (Installed=True) or the RemoteAccess service exists
-
Confirm RRAS service statusRun PowerShell command: Get-Service -Name RemoteAccess | Select-Object -Property Name,StatusAffected if The RemoteAccess service exists and is in any state (running, stopped, or disabled - the vulnerable code is present regardless of service state)
-
Determine Windows Server versionRun PowerShell: [System.Environment]::OSVersion.Version or run 'winver' from command prompt, or check 'systeminfo' output for OS Version/Build numberAffected if Version falls within: Server 2008 (any), Server 2012 (any), Server 2016 < 10.0.14393.7969, Server 2019 < 10.0.17763.7136, Server 2022 < 10.0.20348.3453, Server 2022 23h2 < 10.0.25398.1551, Server 2025 < 10.0.26100.3775
If RRAS is installed and the Windows Server version is lower than the threshold listed for that release family, the environment is affected by CVE-2025-26676.
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 this vulnerability once released. Ensure RRAS is properly firewalled and network access is restricted to authorized personnel to reduce attack surface.
Windows Server 2016: build 10.0.14393.7969 or later; Windows Server 2019: build 10.0.17763.7136 or later; Windows Server 2022: build 10.0.20348.3453 or later; Windows Server 2022 23h2: build 10.0.25398.1551 or later; Windows Server 2025: build 10.0.26100.3775 or later
- Identify the current Windows Server version and build number by running 'winver' or 'systeminfo'
- For Windows Server 2016: Update to build 10.0.14393.7969 or later via Windows Update or by installing the latest cumulative update
- For Windows Server 2019: Update to build 10.0.17763.7136 or later via Windows Update or by installing the latest cumulative update
- For Windows Server 2022: Update to build 10.0.20348.3453 or later via Windows Update or by installing the latest cumulative update
- For Windows Server 2022 23h2: Update to build 10.0.25398.1551 or later via Windows Update or by installing the latest cumulative update
- For Windows Server 2025: Update to build 10.0.26100.3775 or later via Windows Update or by installing the latest cumulative update
- After updating, verify the RRAS service is running properly and test remote access functionality
- Note: Windows Server 2008, 2008 R2, 2012, and 2012 R2 are end-of-life and do not receive security updates for this vulnerability
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-26676 — 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-26676 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