CVE-2025-49663
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 confidenceA heap-based buffer overflow vulnerability exists in Windows Routing and Remote Access Service (RRAS) that allows an unauthenticated remote attacker to execute arbitrary code. The vulnerability stems from improper memory handling in the RRAS service, which listens on the network and processes remote connection requests.
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 installation statusOpen Server Manager, go to Manage > Add Roles and Features, or run 'Get-WindowsFeature -Name Routing' in PowerShell to check if the Routing role is installed. Alternatively, check services list for 'Routing and Remote Access' service (RasMan) existence.Affected if RRAS role is installed on the server - the vulnerability only affects systems with RRAS enabled
-
Confirm RRAS service is runningRun 'Get-Service -Name RemoteAccess' in PowerShell or check services.msc for the RemoteAccess/RAS service status.Affected if RRAS service is running or set to start - the vulnerability is exploitable only when the service is active and listening on the network
-
Identify Windows Server version and build numberRun 'winver' command, or in PowerShell run 'Get-ComputerInfo | Select-Object WindowsProductName, WindowsVersion, OsHardwareAbstractionLayer' to obtain the exact version and build number.Affected if The build number falls below: 14393.8246 (Server 2016), 17763.7558 (Server 2019), 20348.3932 (Server 2022), 25398.1732 (Server 2022 23h2), or 26100.4652 (Server 2025); or if running Server 2008/2012 any version is affected
-
Check network listening status on RRAS portsRun 'netstat -an | findstr LISTENING' and look for ports 1723 (PPTP), 47 (GRE), or other RRAS-related listening ports. Use 'Get-NetTCPConnection -State Listen' for more detail.Affected if RRAS ports are open and listening - indicates the service is accepting remote connections and is exposed to network-based exploitation
A server is affected if it runs a vulnerable Windows Server version (per the build thresholds above) AND has RRAS role installed with the RemoteAccess service running and listening on the network.
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 Windows RRAS immediately. If patches cannot be deployed promptly, disable RRAS if unused or restrict network access to RRAS ports via firewall rules to limit exposure.
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; migrate from EOL versions (2008/2012) to supported Windows Server releases
- Identify current Windows Server version and build number using 'winver' or 'systeminfo'
- Determine if the current build is below the fixed version for your Windows Server release
- For Windows Server 2016: upgrade to build 10.0.14393.8246 or later
- For Windows Server 2019: upgrade to build 10.0.17763.7558 or later
- For Windows Server 2022: upgrade to build 10.0.20348.3932 or later
- For Windows Server 2022 23h2: upgrade to build 10.0.25398.1732 or later
- For Windows Server 2025: upgrade to build 10.0.26100.4652 or later
- For Windows Server 2008/2012: these versions are End-of-Life; migrate to a supported Windows Server version (2019, 2022, or 2025)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49663 — 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-49663 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