CVE-2025-62452
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 · uneditedHeap-based buffer overflow in Windows Routing and Remote Access Service (RRAS) allows an authorized 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 confidenceHeap-based buffer overflow in Windows Routing and Remote Access Service (RRAS) allows an authorized attacker to execute arbitrary code remotely. The vulnerability stems from improper bounds checking in RRAS handling of network requests, enabling heap memory corruption.
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< 10.0.14393.8594< 10.0.17763.8027< 10.0.19044.6575< 10.0.19045.6575< 10.0.22631.6199< 10.0.26100.7092< 10.0.26200.7092all versions= r2CVSS 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
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm RRAS is installed or enabledRun 'Get-WindowsOptionalFeature -Online -FeatureName RemoteAccess' in PowerShell and check the State property, or run 'Get-Service RemoteAccess' to check if the service exists.Affected if RRAS State is Enabled or the RemoteAccess service exists and is not disabled.
-
Check Windows build numberRun 'winver' and note the build number displayed, or run '[System.Environment]::OSVersion.Version' in PowerShell to get the exact version string.Affected if The build number is lower than the thresholds: Windows 10 1607 < 14393.8594, 1809 < 17763.8027, 21h2 < 19044.6575, 22h2 < 19045.6575; Windows 11 23h2 < 22631.6199, 24h2 < 26100.7092, 25h2 < 26200.7092; or Windows Server 2008 R2 any version.
-
Verify RRAS service statusRun 'Get-Service RemoteAccess' in PowerShell. If the service exists, check the Status column.Affected if The service Status is Running. A stopped service reduces but does not eliminate risk if the binary is still present.
-
Identify RRAS components loadedCheck the registry key 'HKLM\SYSTEM\CurrentControlSet\Services\RemoteAccess' for the ImagePath value to confirm RRAS binaries are present on the system.Affected if The ImagePath points to valid RRAS binaries (typically in System32 folder).
The system is affected only if RRAS is installed or enabled AND the Windows version falls within the listed affected build ranges, as the buffer overflow requires the vulnerable RRAS code to be present.
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.859410.0.17763.802710.0.19044.6575
Apply Microsoft security updates for CVE-2025-62452. If patching is delayed, consider disabling RRAS if not required, or restricting network access to RRAS interfaces via firewall rules.
Apply Microsoft security update KB for CVE-2025-62452; no specific version upgrade required as patches contain the fix
- Identify the Windows version and build number by running 'winver' or 'systeminfo'
- Navigate to Microsoft Update Catalog (update.microsoft.com) or use Windows Update to check for the security update corresponding to CVE-2025-62452
- Apply the appropriate Windows security update for your version - the minimum fixed builds are: Windows 10 1607: 10.0.14393.8594, Windows 10 1809: 10.0.17763.8027, Windows 10 21h2: 10.0.19044.6575, Windows 10 22h2: 10.0.19045.6575, Windows 11 23h2: 10.0.22631.6199, Windows 11 24h2: 10.0.26100.7092, Windows 11 25h2: 10.0.26200.7092
- Restart the system after applying the update
- Verify the installed update by checking 'Installed Updates' in Control Panel or running 'Get-HotFix' in PowerShell
- For Windows Server 2008: Microsoft Extended Support ended in 2020; apply the out-of-band security update from MSRC if available, or consider migrating to a supported Windows Server version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-62452 — 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-62452 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