CVE-2025-49688
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 · uneditedDouble free 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 double-free memory corruption vulnerability exists in Windows Routing and Remote Access Service (RRAS). This flaw allows an unauthenticated remote attacker to execute arbitrary code by exploiting the memory management error where memory is freed twice, leading to heap corruption and potentially gaining code execution privileges.
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= 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 installedOpen Server Manager, go to 'Manage' > 'Add Roles and Features', or run 'Get-WindowsFeature -Name Routing' in PowerShell to check if the Remote Access role with Routing role service is installedAffected if RRAS role is not installed - the vulnerability cannot be exploited on systems without this role
-
Check if RRAS service is runningRun 'Get-Service -Name RemoteAccess' in PowerShell or open Services console and locate 'Routing and Remote Access' service to check its statusAffected if The RemoteAccess service is running - the vulnerability is only exploitable when the RRAS service is active
-
Determine Windows Server version and buildRun 'winver' command, or execute 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' in Command Prompt, or use 'Get-ComputerInfo | Select-Object WindowsProductName, WindowsVersion, OsHardwareAbstractionLayer' in PowerShellAffected if The server version matches any of the affected versions (Server 2012 R2, 2016, 2019, 2022, 2022 23h2, or 2025) and the build number is below the patched threshold for that version
-
Compare build number against patched versionsRun 'winver' to get the exact build number, then compare: Server 2016 needs >= 10.0.14393.8246, Server 2019 needs >= 10.0.17763.7558, Server 2022 needs >= 10.0.20348.3932, Server 2022 23h2 needs >= 10.0.25398.1732, Server 2025 needs >= 10.0.26100.4652, Server 2012 R2 has no patch listedAffected if The installed build number is lower than the corresponding patched version for your Windows Server release, indicating the system is vulnerable
A system is affected if RRAS is installed and running, and its Windows Server version and build number fall within the affected ranges and are below the patched thresholds.
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 the Microsoft security update for CVE-2025-49688 when released. If immediate patching is not feasible, disable RRAS if not required, or enforce network-level access controls to limit exposure to trusted sources only.
Apply the CVE-2025-49688 security update to reach the minimum fixed build number for your Windows Server version (2016+: see version thresholds; Windows Server 2012 R2 is end-of-life and no longer receives security updates)
- Check current RRAS server version by running 'winver' or 'systeminfo' in Command Prompt
- Open Windows Update: Start > Settings > Update & Security > Windows Update
- Click 'Check for updates' and install all available security updates
- For manual download, visit Microsoft Update Catalog (catalog.update.microsoft.com) and search for the CVE-2025-49688 security update for your Windows Server version
- After installation, restart the server to complete the patch deployment
- Verify the patch is installed by checking the installed updates list or running 'winver' to confirm the build number meets or exceeds: Windows Server 2016: 10.0.14393.8246 | Windows Server 2019: 10.0.17763.7558 | Windows Server 2022: 10.0.20348.3932 | Windows Server 2022 23h2: 10.0.25398.1732 | Windows Server 2025: 10.0.26100.4652
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49688 — 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-49688 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