CVE-2025-53798
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 · uneditedBuffer over-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 confidenceA buffer over-read vulnerability in Windows Routing and Remote Access Service (RRAS) allows an unauthenticated remote attacker to read sensitive memory contents beyond intended boundaries, potentially disclosing configuration data or other information from the affected system's memory.
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 role is installedOpen Server Manager, select the server, go to Manage > Add Roles and Features, or run Get-WindowsFeature -Name Routing in PowerShell to check if the 'Routing' role is installedAffected if RRAS (Routing and Remote Access Service) is installed or enabled on the server - this is required for the vulnerability to be exploitable
-
Confirm RRAS service statusRun Get-Service -Name RemoteAccess in PowerShell or check the RemoteAccess service in Services.msc to see if the service is runningAffected if The RemoteAccess service (RRAS) is running - an attacker would need network access to the RRAS service to trigger the buffer over-read
-
Check Windows Server version and build numberRun winver or run systeminfo in Command Prompt, or use PowerShell with [System.Environment]::OSVersion.Version or Get-ComputerInfo to retrieve the exact Windows build numberAffected if The Windows Server version falls within the affected ranges: Server 2008/2012 (any version), Server 2016 < build 14393.8422, Server 2019 < build 17763.7792, Server 2022 < build 20348.4106, Server 2022 23H2 < build 25398.1849, or Server 2025 < build 26100.6508
-
Confirm RRAS protocol bindingsIn Server Manager > Tools > Routing and Remote Access, right-click the server > Properties, or check registry key HKLM\System\CurrentControlSet\Services\RemoteAccess\Parameters to see if RRAS is configured to accept connectionsAffected if RRAS is configured with active protocol bindings (IP, IPX, or AppleTalk) that accept incoming connections - this exposes the vulnerable code to network attackers
A server is affected if RRAS is installed and enabled, the Windows Server version matches the affected build ranges, and RRAS is configured to accept network connections, allowing an unauthenticated remote attacker to trigger the buffer over-read.
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 patches for CVE-2025-53798 to affected Windows servers running RRAS, or disable the RRAS role if not required in the environment.
Windows Server 2016 to 10.0.14393.8422+ | Windows Server 2019 to 10.0.17763.7792+ | Windows Server 2022 to 10.0.20348.4106+ | Windows Server 2022 23h2 to 10.0.25398.1849+ | Windows Server 2025 to 10.0.26100.6508+
- Identify the current Windows Server version by running 'winver' or 'systeminfo' in Command Prompt
- For Windows Server 2016: Apply update KB5055520 or later to reach version 10.0.14393.8422
- For Windows Server 2019: Apply update KB5055523 or later to reach version 10.0.17763.7792
- For Windows Server 2022: Apply update KB5055518 or later to reach version 10.0.20348.4106
- For Windows Server 2022 23h2: Apply update KB5055519 or later to reach version 10.0.25398.1849
- For Windows Server 2025: Apply update KB5055525 or later to reach version 10.0.26100.6508
- Verify the fix by checking the updated version matches or exceeds the target build number
- Restart the server after applying the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.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,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-53798 — 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-53798 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