dbcve.org
Windows Server 2012Operating system · Microsoft

CVE-2025-54106

HIGH · 8.8 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 →
95/100
Remediation priority · Urgent
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
Integer overflow or wraparound in Windows Routing and Remote Access Service (RRAS) allows an unauthorized attacker to execute code 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

Integer overflow in Windows Routing and Remote Access Service (RRAS) allows remote attackers to achieve code execution by exploiting the wraparound vulnerability in the network-exposed service.

MitigationApply Microsoft security patches for CVE-2025-54106 when released; if immediate patch unavailable, restrict network access to RRAS servers via firewall rules and disable RRAS if not required.

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 2012Operating system
Affected:= 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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 system
    Open Server Manager, go to Manage > Add Roles and Features, check if 'Remote Access' role with 'Routing' role service is installed. Alternatively, run 'Get-WindowsFeature -Name RemoteAccess' in PowerShell to list installed roles.
    Affected if RRAS role is installed and the server is running an affected Windows Server version
  2. Confirm RRAS service is running
    Open Services console (services.msc) and check if 'Routing and Remote Access' service status is Running, or run 'Get-Service RemoteAccess' in PowerShell.
    Affected if RRAS service is running and the server is running an affected Windows Server version
  3. Identify Windows Server version and build number
    Run 'winver' from command prompt or use 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to get the exact version and build number.
    Affected if Windows Server version matches any of the affected versions listed in the CVE
  4. Compare installed version against affected ranges
    Match your build number (e.g., 10.0.14393.xxxx) against the CVE thresholds: 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. For Server 2012 R2, any version is affected if unpatched.
    Affected if Build number is lower than the CVE threshold for your Windows Server version

You are affected if RRAS is installed and running on an unpatched Windows Server 2012 R2, 2016, 2019, 2022, 2022 23h2, or 2025 version below the specified build thresholds.

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 Microsoft security patches for CVE-2025-54106 when released; if immediate patch unavailable, restrict network access to RRAS servers via firewall rules and disable RRAS if not required.

Recommended fix High confidence

Windows Server 2016 build 10.0.14393.8422 or later; Windows Server 2019 build 10.0.17763.7792 or later; Windows Server 2022 build 10.0.20348.4106 or later; Windows Server 2022 23h2 build 10.0.25398.1849 or later; Windows Server 2025 build 10.0.26100.6508 or later

  1. Identify the current Windows Server version by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine which Windows Server 2016/2019/2022/2022 23h2/2025 build number is currently installed
  3. Apply the appropriate Windows Security Update: For Server 2016, install build 10.0.14393.8422 or later; For Server 2019, install build 10.0.17763.7792 or later; For Server 2022, install build 10.0.20348.4106 or later; For Server 2022 23h2, install build 10.0.25398.1849 or later; For Server 2025, install build 10.0.26100.6508 or later
  4. Restart the server after applying the update
  5. Verify the update was installed successfully by checking the build number again
  6. Note: Windows Server 2012 R2 reached end of support and requires upgrade to a supported version (2016 or later)
Caveat Windows Server 2012 R2 is end-of-life with no security updates; upgrading to a newer server OS may require application compatibility testing

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

Fix this in Windows Server 2012 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,540
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,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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