CVE-2025-29959
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 confidenceThis is an information disclosure vulnerability in Windows Routing and Remote Access Service (RRAS) caused by use of an uninitialized resource. An unauthenticated remote attacker can exploit this to read sensitive data from uninitialized memory structures, potentially exposing kernel or previous session data over the network.
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.10240.21014< 10.0.14393.8066< 10.0.17763.7314< 10.0.19044.5854< 10.0.19045.5854< 10.0.22621.5335< 10.0.22631.5335< 10.0.26100.4061CVSS 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 is installed or enabledOpen Services console (services.msc) and look for 'Routing and Remote Access' service, or run 'netsh routing ip show global' to check RRAS statusAffected if RRAS service is installed and running on the system
-
Check Windows versionRun 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' from command promptAffected if Windows version falls below any of the following thresholds: 10.0.10240.21014 (1507), 10.0.14393.8066 (1607), 10.0.17763.7314 (1809), 10.0.19044.5854 (21h2), 10.0.19045.5854 (22h2), 10.0.22621.5335 (11 22h2), 10.0.22631.5335 (11 23h2), 10.0.26100.4061 (11 24h2)
-
Confirm network exposure of RRASRun 'netsh routing ip show interface' to list RRAS interfaces; check firewall rules for RRAS-related ports (typically PPTP/L2TP/IKEv2 ports 1723, 500, 4500)Affected if RRAS is listening on external or untrusted network interfaces rather than only on internal/loopback adapters
The system is affected only if both RRAS is enabled AND the Windows version is below the patched thresholds AND RRAS is network-accessible to untrusted sources.
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.10240.2101410.0.14393.806610.0.17763.7314
Apply the relevant Microsoft security patch for this vulnerability through Windows Update or manual security update deployment. Ensure RRAS is only exposed to trusted networks since the attack is network-available.
Windows 10 1507: build 10.0.10240.21014+ | Windows 10 1607: build 10.0.14393.8066+ | Windows 10 1809: build 10.0.17763.7314+ | Windows 10 21h2: build 10.0.19044.5854+ | Windows 10 22h2: build 10.0.19045.5854+ | Windows 11 22h2: build 10.0.22621.5335+ | Windows 11 23h2: build 10.0.22631.5335+ | Windo
- Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
- Determine which Windows 10 or 11 release (e.g., 1507, 1607, 1809, 21h2, 22h2, 22h2, 23h2, 24h2) is currently installed
- Based on the installed release, upgrade to or beyond the fixed build version: For Windows 10 1507, upgrade to build 10.0.10240.21014 or later; For Windows 10 1607, upgrade to build 10.0.14393.8066 or later; For Windows 10 1809, upgrade to build 10.0.17763.7314 or later; For Windows 10 21h2, upgrade to build 10.0.19044.5854 or later; For Windows 10 22h2, upgrade to build 10.0.19045.5854 or later; F
- Apply updates via Windows Update, or download the corresponding Security Update from the Microsoft Update Catalog for the specific Windows version
- After patching, verify the RRAS service is running the patched version and confirm the build number matches or exceeds the fixed 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-29959 — 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-29959 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