dbcve.org
Windows Server 2008Operating system · Microsoft

CVE-2025-54113

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
Heap-based buffer overflow 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

Heap-based buffer overflow in Windows Routing and Remote Access Service (RRAS) enables an unauthenticated remote attacker to execute arbitrary code by overflowing a heap-allocated buffer, likely through specially crafted network packets to the RRAS service.

MitigationApply Microsoft security patches for CVE-2025-54113 immediately; if patching is not immediately feasible, disable RRAS if not required or restrict network access to the RRAS service via firewall rules.

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
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 enabled
    Open Server Manager, go to Manage > Add Roles and Features, or check Services console (services.msc) for 'Routing and Remote Access' service status. Alternatively, run 'netsh routing ip show status' from an elevated command prompt.
    Affected if RRAS service is running or enabled on the system
  2. Confirm Windows Server version
    Run 'winver' from Start menu or execute 'systeminfo' in Command Prompt and note the OS Version and Build number displayed in the output.
    Affected if Version matches any of these affected builds: 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
  3. Check installed security updates
    Open Control Panel > Programs > View installed updates, or run 'wmic qfe list' / 'Get-HotFix' in PowerShell, and look for Microsoft security updates released after the CVE publication date.
    Affected if No security update for CVE-2025-54113 is listed among installed patches

The system is affected if RRAS is enabled and the Windows Server version/build is lower than the fixed versions listed, or if the corresponding security patch is not installed.

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-54113 immediately; if patching is not immediately feasible, disable RRAS if not required or restrict network access to the RRAS service via firewall rules.

Recommended fix Moderate 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. Ensure Automatic Updates is enabled on the Windows Server system
  2. Run Windows Update and install all available security updates, or manually check for the specific KB for CVE-2025-54113 at https://msrc.microsoft.com/
  3. Restart the server if prompted after installing updates
  4. Verify the RRAS service is running properly after updates
Caveat Windows Server 2008 and 2012 are end-of-life and receive no security updates; ensure application compatibility before applying updates to supported versions

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-54113 — 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-54113 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