dbcve.org
Windows Server 2008Operating system · Microsoft

CVE-2025-26664

MEDIUM · 6.5 CVSS v3.1 Published 2025-04-08
Fix available
A fix is available. Upgrade to 10.0.14393.7969 / 10.0.17763.7136 or later.
See remediation →
72/100
Remediation priority · Elevated
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
Buffer 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 · high confidence

A buffer over-read vulnerability exists in Windows Routing and Remote Access Service (RRAS) that allows an unauthenticated remote attacker to read sensitive memory contents, potentially disclosing information such as credentials, session tokens, or other data from the server's memory.

MitigationApply the Microsoft security update for CVE-2025-26664 to all affected Windows servers running RRAS. If RRAS is not required, consider disabling it to reduce the attack surface.

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 Server 2008Operating system
Affected:all versions= r2
Windows Server 2012Operating system
Affected:all versions= r2
Windows Server 2016Operating system
Affected:< 10.0.14393.7969
Windows Server 2019Operating system
Affected:< 10.0.17763.7136
Windows Server 2022Operating system
Affected:< 10.0.20348.3453
Windows Server 2022 23h2Operating system
Affected:< 10.0.25398.1551
Windows Server 2025Operating system
Affected:< 10.0.26100.3775

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify RRAS is installed on the server
    Open Server Manager, select the server, and check under 'Add Roles and Features' to see if 'Remote Access' role with 'Routing' role service is installed. Alternatively, run 'Get-WindowsFeature -Name Routing' in PowerShell on the server.
    Affected if RRAS role is installed and the server OS version falls within the affected ranges below.
  2. Check Windows Server version and build number
    Run 'winver' from Run dialog, or execute 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' in Command Prompt, or use 'Get-ComputerInfo | Select-Object WindowsProductName, WindowsVersion, OsHardwareAbstractionLayer' in PowerShell.
    Affected if The server is running Windows Server 2008, 2012 (any version), or 2016/2019/2022/2022 23h2/2025 with a build number below the fixed versions.
  3. Confirm build number for Windows Server 2016
    If running Windows Server 2016, verify the build number is below 10.0.14393.7969. Run 'winver' or check the version via 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuild' and compare.
    Affected if Build number is less than 10.0.14393.7969.
  4. Confirm build number for Windows Server 2019
    If running Windows Server 2019, verify the build number is below 10.0.17763.7136. Check via 'winver' or the registry method above.
    Affected if Build number is less than 10.0.17763.7136.
  5. Confirm build number for Windows Server 2022 and later
    If running Windows Server 2022, 2022 23h2, or 2025, verify the respective build numbers: 2022 < 10.0.20348.3453, 2022 23h2 < 10.0.25398.1551, 2025 < 10.0.26100.3775. Check via 'winver' or the registry method above.
    Affected if Build number is less than the respective fixed version for that Windows Server release.

The server is affected if RRAS is installed and the Windows Server version matches one of the affected versions with a build number below the fixed threshold.

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.7969 / 10.0.17763.7136 / 10.0.20348.3453 or later
Fixed in 10.0.14393.796910.0.17763.713610.0.20348.3453
Interim mitigation

Apply the Microsoft security update for CVE-2025-26664 to all affected Windows servers running RRAS. If RRAS is not required, consider disabling it to reduce the attack surface.

Recommended fix High confidence

March 2025 security updates for Windows Server (KB5011570 or later depending on version)

  1. Check current Windows Server version by running 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"'
  2. Ensure Windows Update is enabled and configured
  3. Run Windows Update to install the latest security updates, or manually download the specific update from the Microsoft Update Catalog for this CVE
  4. After installation, verify the version meets the minimum build number: Windows Server 2016 >= 10.0.14393.7969, Windows Server 2019 >= 10.0.17763.7136, Windows Server 2022 >= 10.0.20348.3453, Windows Server 2022 23h2 >= 10.0.25398.1551, Windows Server 2025 >= 10.0.26100.3775
  5. Restart the server if prompted
Caveat Patches for RRAS should be low risk; test in non-production environment before deploying broadly

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

Fix this in Windows Server 2008 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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 locally
dbcve dependency scanner

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