CVE-2025-54095
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 · uneditedOut-of-bounds 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 confidenceAn out-of-bounds read vulnerability exists in Windows Routing and Remote Access Service (RRAS) that allows an unauthenticated remote attacker to read sensitive information from memory by sending specially crafted network requests to the RRAS service.
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.8422< 10.0.17763.7792< 10.0.20348.4106< 10.0.25398.1849< 10.0.26100.6508CVSS 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 service is installedRun PowerShell command: Get-WindowsFeature -Name *RemoteAccess* or check registry key HKLM\SYSTEM\CurrentControlSet\Services\RemoteAccessAffected if RRAS is installed on the system
-
Confirm RRAS service is running or enabledRun PowerShell: Get-Service -Name RemoteAccess or check if the RemoteAccess service is startedAffected if The RemoteAccess service is running or set to start automatically (this is required for the vulnerable code path to be exposed)
-
Identify Windows Server versionRun: winver or PowerShell: [Environment]::OSVersion or systeminfo | findstr /B /C:"OS Version"Affected if The installed version falls within the affected ranges: Server 2008 (all), Server 2012 (all), Server 2016 < 10.0.14393.8422, Server 2019 < 10.0.17763.7792, Server 2022 < 10.0.20348.4106, Server 2022 23h2 < 10.0.25398.1849, Server 2025 < 10.0.26100.6508
-
Check specific build number if applicableRun PowerShell: (Get-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion').CurrentBuild and compare against the version-specific thresholds aboveAffected if Build number is lower than the patched version for your Windows Server release
System is affected if RRAS is installed and running on a Windows Server version within the affected build ranges; if RRAS is disabled or on a fully patched version, the system is likely not affected.
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.842210.0.17763.779210.0.20348.4106
Apply Microsoft security updates for this vulnerability once released; if patches are unavailable, evaluate disabling RRAS on non-critical systems or implementing network segmentation to limit RRAS exposure to trusted networks.
Windows Server 2016: 10.0.14393.8422 | Windows Server 2019: 10.0.17763.7792 | Windows Server 2022: 10.0.20348.4106 | Windows Server 2022 23h2: 10.0.25398.1849 | Windows Server 2025: 10.0.26100.6508
- Identify the current Windows Server version by running 'winver' or 'systeminfo' in Command Prompt
- Determine which Windows Server version family applies (2016, 2019, 2022, 2022 23h2, or 2025)
- For Windows Server 2016: Upgrade to build 10.0.14393.8422 or later by installing the latest cumulative update
- For Windows Server 2019: Upgrade to build 10.0.17763.7792 or later by installing the latest cumulative update
- For Windows Server 2022: Upgrade to build 10.0.20348.4106 or later by installing the latest cumulative update
- For Windows Server 2022 23h2: Upgrade to build 10.0.25398.1849 or later by installing the latest cumulative update
- For Windows Server 2025: Upgrade to build 10.0.26100.6508 or later by installing the latest cumulative update
- Verify the update was applied successfully by checking the build number again after reboot
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing2.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 $3,488.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54095 — 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-54095 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