dbcve.org
Windows Server 2008Operating system · Microsoft

CVE-2025-54097

MEDIUM · 6.5 CVSS v3.1 Published 2025-09-09
Fix available
A fix is available. Upgrade to 10.0.14393.8422 / 10.0.17763.7792 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
Out-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 confidence

An out-of-bounds read vulnerability in Windows Routing and Remote Access Service (RRAS) allows an unauthenticated remote attacker to read arbitrary memory contents over the network, potentially disclosing sensitive information such as configuration data or session tokens.

MitigationApply the Microsoft security update for CVE-2025-54097 to all affected Windows servers running RRAS. If immediate patching is not feasible, restrict network access to RRAS servers using firewalls or network segmentation to limit exposure to trusted networks only.

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.8422
Windows Server 2019Operating system
Affected:< 10.0.17763.7792
Windows Server 2022Operating system
Affected:< 10.0.20348.4106
Windows Server 2022 23h2Operating system
Affected:< 10.0.25398.1849
Windows Server 2025Operating system
Affected:< 10.0.26100.6508

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. Check Windows Server version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to retrieve the installed Windows Server version and build number.
    Affected if The version is older than 10.0.14393.8422 (Server 2016), 10.0.17763.7792 (Server 2019), 10.0.20348.4106 (Server 2022), 10.0.25398.1849 (Server 2022 23h2), or 10.0.26100.6508 (Server 2025); or if running Server 2008 or Server 2012 of any version.
  2. Verify RRAS service is installed
    Open Services console (services.msc) and locate 'Routing and Remote Access', or run 'sc query RemoteAccess' to query the service status.
    Affected if The RRAS service exists on the system (even if disabled, the binary may still be vulnerable).
  3. Confirm RRAS is enabled or running
    Check the service status in Services console or run 'sc query RemoteAccess' to see if the service state is Running, Started, or manually enabled.
    Affected if RRAS is enabled, started, or configured to start automatically (the vulnerability is exploitable when RRAS is active).
  4. Check RRAS configuration via registry
    Inspect the registry key HKLM\System\CurrentControlSet\Services\RemoteAccess for the 'Start' value (2 = auto, 3 = manual, 4 = disabled) and verify if RRAS is configured.
    Affected if The 'Start' value is set to 2 (auto-start) or 3 (manual), indicating RRAS can be activated.
  5. Identify network exposure of RRAS
    Review firewall rules or network configuration to determine if RRAS ports (default L2TP/PPTP ports or custom RRAS ports) are exposed to untrusted networks.
    Affected if RRAS is accessible over the network to unauthenticated attackers (the vulnerability is remotely exploitable).

A system is affected if it runs a vulnerable Windows Server version (as listed in the affected ranges) AND has RRAS installed and enabled or capable of being enabled, with network accessibility to untrusted actors.

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.8422 / 10.0.17763.7792 / 10.0.20348.4106 or later
Fixed in 10.0.14393.842210.0.17763.779210.0.20348.4106
Interim mitigation

Apply the Microsoft security update for CVE-2025-54097 to all affected Windows servers running RRAS. If immediate patching is not feasible, restrict network access to RRAS servers using firewalls or network segmentation to limit exposure to trusted networks only.

Recommended fix High confidence

Upgrade to the build versions listed above (e.g., Windows Server 2019 10.0.17763.7792 or later). For Windows Server 2008/2012 (all versions), migrate to a supported Windows Server version as these are end-of-life and receive no security updates.

  1. 1. Check the current Windows Server version by running `winver` or `systeminfo` in Command Prompt
  2. 2. For Windows Server 2016 and later: Run Windows Update (`ms-settings:windowsupdate`) or use WSUS to check for and install the security update corresponding to this CVE
  3. 3. Alternatively, download and install the specific monthly security update from the Microsoft Update Catalog that matches your Windows version (KB5XXXXX)
  4. 4. After installation, restart the server to apply the patches
  5. 5. Verify the fix by checking that the build number matches or exceeds: 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
Caveat Windows Server 2008 and 2012 have no security patches available; migration to a supported version is required. Test updates in a staging environment before production deployment.

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

Fix this in Windows Server 2008 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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