CVE-2025-27474
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 · uneditedUse of uninitialized resource 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 confidenceUse of an uninitialized resource in Windows Routing and Remote Access Service (RRAS) allows an unauthorized remote attacker to disclose sensitive information. The vulnerability is exploitable over a network without authentication and carries a CVSS 6.5 (Medium) severity rating.
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.7969< 10.0.17763.7136< 10.0.20348.3453< 10.0.25398.1551< 10.0.26100.3775CVSS 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, go to 'Add Roles and Features', check if 'Remote Access' role with 'Routing' role service is installed. Alternatively, run 'Get-WindowsFeature -Name Routing' in PowerShell on Windows Server.Affected if RRAS role with Routing is installed and enabled on the server
-
Check if RRAS service is runningOpen Services console (services.msc) and locate 'Routing and Remote Access' service, or run 'Get-Service RemoteAccess' in PowerShell.Affected if The RemoteAccess service status is Running or Started
-
Determine Windows Server version and buildRun 'winver' from command prompt, or execute 'Get-ComputerInfo | Select-Object WindowsProductName, OsVersion, OsBuildNumber' in PowerShell.Affected if Build number is below: 14393.7969 (Server 2016), 17763.7136 (Server 2019), 20348.3453 (Server 2022), 25398.1551 (Server 2022 23h2), 26100.3775 (Server 2025); or if running Server 2008/2012 any version (all versions affected)
-
Confirm RRAS is remotely accessibleCheck network listening ports: run 'netstat -an | findstr :1723' for PPTP and verify RRAS is bound to network interfaces. In Routing and Remote Access console, verify the server is configured to accept connections.Affected if RRAS is configured to accept remote connections and is bound to a network interface accessible over the network
A server is affected if it runs a vulnerable Windows Server version listed above AND has the RRAS Routing role installed and enabled, as the vulnerability exists specifically within the RRAS component.
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.796910.0.17763.713610.0.20348.3453
Apply the relevant Microsoft security update for this vulnerability. If RRAS is not required, disable the service to reduce attack surface.
Windows Server 2016: build 10.0.14393.7969 | Windows Server 2019: build 10.0.17763.7136 | Windows Server 2022: build 10.0.20348.3453 | Windows Server 2022 23h2: build 10.0.25398.1551 | Windows Server 2025: build 10.0.26100.3775
- Identify the installed Windows Server version by running 'winver' or 'systeminfo' in Command Prompt
- Determine which Windows Server edition applies from the affected versions list
- For Windows Server 2016: Apply KB5010351 (or subsequent security update) to reach build 10.0.14393.7969 or later
- For Windows Server 2019: Apply KB5010354 (or subsequent security update) to reach build 10.0.17763.7136 or later
- For Windows Server 2022: Apply KB5010359 (or subsequent security update) to reach build 10.0.20348.3453 or later
- For Windows Server 2022 23h2: Apply KB5010358 (or subsequent security update) to reach build 10.0.25398.1551 or later
- For Windows Server 2025: Apply KB5010352 (or subsequent security update) to reach build 10.0.26100.3775 or later
- Restart the server after applying the security update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27474 — 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-27474 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