dbcve.org
Windows Server 2008Operating system · Microsoft

CVE-2025-55225

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 memory contents beyond allocated buffer boundaries, potentially exposing sensitive system information over the network.

MitigationApply the Microsoft security update for CVE-2025-55225 through Windows Update or enterprise patch management, then verify RRAS continues to function correctly.

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. Identify Windows Server version and build number
    Run `systeminfo` or `Get-ComputerInfo | Select-Object WindowsVersion,OsVersion,OsBuildNumber` to obtain the installed Windows build
    Affected if Build number is below 14393.8422 (Server 2016), 17763.7792 (Server 2019), 20348.4106 (Server 2022), 25398.1849 (Server 2022 23h2), 26100.6508 (Server 2025), or if running any version of Server 2008 or Server 2012 (all versions are affected)
  2. Determine if RRAS role is installed
    Run `Get-WindowsFeature -Name Remote-Access` or check for the presence of the RemoteAccess service via `Get-Service RemoteAccess`
    Affected if The Remote Access role or Routing and Remote Access (RRAS) feature is installed on the server
  3. Check if RRAS service is enabled or running
    Run `Get-Service RemoteAccess` and check the Status property, or inspect the service via Services.msc
    Affected if The RemoteAccess service is in a Running, Started, or Auto-start state on the system

The system is affected only if it is running a vulnerable Windows Server version within the affected build ranges AND has RRAS installed and enabled, exposing the out-of-bounds read vulnerability to network attackers.

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-55225 through Windows Update or enterprise patch management, then verify RRAS continues to function correctly.

Recommended fix High confidence

Upgrade to Windows Server 2016 build 10.0.14393.8422 or later, Server 2019 build 10.0.17763.7792 or later, Server 2022 build 10.0.20348.4106 or later, Server 2022 23h2 build 10.0.25398.1849 or later, or 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 build version is currently installed (e.g., for Server 2019, check if below 10.0.17763.7792)
  3. For Windows Server 2016, 2019, 2022, 2022 23h2, and 2025: Apply the latest Windows Update or manually download and install the security update corresponding to build 10.0.14393.8422, 10.0.17763.7792, 10.0.20348.4106, 10.0.25398.1849, or 10.0.26100.6508 respectively
  4. For Windows Server 2008 and 2012: These versions are end-of-life and no longer receive security updates; migrate to a supported Windows Server version (2016 or later)
  5. After patching, verify the RRAS service version matches the fixed build number using 'sc queryex type= service' and check Windows Update history for the installed security update
Caveat Windows Server 2008 and 2012 are end-of-life with no security updates; migration to newer OS required; ensure application compatibility before upgrading

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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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