CVE-2025-47998
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 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 confidenceHeap-based buffer overflow vulnerability in Windows Routing and Remote Access Service (RRAS) enables unauthenticated remote attackers to execute arbitrary code via network exploitation. The flaw exists in how RRAS handles network traffic, allowing heap memory corruption that can be leveraged for code execution.
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.8246< 10.0.17763.7558< 10.0.20348.3932< 10.0.25398.1732< 10.0.26100.4652CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify RRAS role is installed on the serverOpen Server Manager, go to Manage > Add Roles and Features, check if 'Remote Access' role with 'Routing' role service is installed; or run Get-WindowsFeature -Name Routing in PowerShellAffected if RRAS role is installed and the server version falls within the affected build ranges
-
Confirm RRAS service is runningRun 'Get-Service RemoteAccess' in PowerShell or check Services.msc for the 'Remote Access' service statusAffected if RemoteAccess service is in Running state
-
Check Windows Server version and build numberRun 'winver' or execute '[System.Environment]::OSVersion.Version' and 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' in Command PromptAffected if Version matches an affected release (2008/2012 all builds, 2016 < 10.0.14393.8246, 2019 < 10.0.17763.7558, 2022 < 10.0.20348.3932, 2022 23h2 < 10.0.25398.1732, 2025 < 10.0.26100.4652)
-
Verify RRAS routing functionality is configuredOpen Routing and Remote Access snap-in (rrasmgmt.msc) or run 'netsh routing ip show config' to check if any routing interfaces are enabledAffected if RRAS has active routing interfaces configured and accepting network traffic
The server is affected if RRAS is installed and running on a Windows Server version with a build number below the thresholds listed for each supported release.
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.824610.0.17763.755810.0.20348.3932
Apply Microsoft security updates for CVE-2025-47998 when available; if RRAS is not required, disable the service; ensure network segmentation and firewall rules restrict RRAS-related ports (default RPC/L2TP/IPSec ports) to minimize attack surface.
Windows Server 2016 build 10.0.14393.8246, Windows Server 2019 build 10.0.17763.7558, Windows Server 2022 build 10.0.20348.3932, Windows Server 2022 23h2 build 10.0.25398.1732, Windows Server 2025 build 10.0.26100.4652
- Apply the relevant Microsoft security update for this vulnerability (KB reference available via MSRC at msrc.microsoft.com)
- For Windows Server 2016 and later: Install the latest cumulative update that includes the fix for this RRAS vulnerability
- For Windows Server 2022: Ensure build is 10.0.20348.3932 or later
- For Windows Server 2022 23h2: Ensure build is 10.0.25398.1732 or later
- For Windows Server 2025: Ensure build is 10.0.26100.4652 or later
- For Windows Server 2019: Ensure build is 10.0.17763.7558 or later
- For Windows Server 2016: Ensure build is 10.0.14393.8246 or later
- 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
- Testing3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47998 — 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-47998 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