dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-29960

MEDIUM · 6.5 CVSS v3.1 Published 2025-05-13
Fix available
A fix is available. Upgrade to 10.0.10240.21014 / 10.0.14393.8066 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Out-of-bounds read 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 confidence

An out-of-bounds read vulnerability exists in Windows Routing and Remote Access Service (RRAS) that allows an unauthenticated remote attacker to read sensitive memory contents beyond intended boundaries, potentially disclosing heap or stack data from the RRAS process.

MitigationApply the relevant Microsoft security update for CVE-2025-29960 through Windows Update or WSUS. If RRAS is not required, consider disabling the service to reduce attack surface.

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
Windows 10 1507Operating system
Affected:< 10.0.10240.21014
Windows 10 1607Operating system
Affected:< 10.0.14393.8066
Windows 10 1809Operating system
Affected:< 10.0.17763.7314
Windows 10 21h2Operating system
Affected:< 10.0.19044.5854
Windows 10 22h2Operating system
Affected:< 10.0.19045.5854
Windows 11 22h2Operating system
Affected:< 10.0.22621.5335
Windows 11 23h2Operating system
Affected:< 10.0.22631.5335
Windows 11 24h2Operating system
Affected:< 10.0.26100.4061

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify RRAS service status
    Open Services.msc or run 'Get-Service RemoteAccess' in PowerShell to check if the RemoteAccess (RRAS) service is installed and running on the system
    Affected if The RemoteAccess service is present and running - this is the vulnerable component that must be present for the flaw to be exploitable
  2. Check Windows 10 build number
    Run 'winver' or execute 'Get-ComputerInfo | Select-Object WindowsVersion, OsVersion, OsBuildNumber' in PowerShell to obtain the exact Windows 10 build version
    Affected if The installed version is less than 10.0.10240.21014 (1507), 10.0.14393.8066 (1607), 10.0.17763.7314 (1809), 10.0.19044.5854 (21h2), or 10.0.19045.5854 (22h2) depending on your Windows 10 release
  3. Check Windows 11 build number
    Run 'winver' or execute 'Get-ComputerInfo | Select-Object WindowsVersion, OsVersion, OsBuildNumber' in PowerShell to obtain the exact Windows 11 build version
    Affected if The installed version is less than 10.0.22621.5335 (22h2), 10.0.22631.5335 (23h2), or 10.0.26100.4061 (24h2) depending on your Windows 11 release

Your system is affected only if RRAS (RemoteAccess service) is enabled AND your Windows build number falls below the listed threshold for your specific Windows version.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 10.0.10240.21014 / 10.0.14393.8066 / 10.0.17763.7314 or later
Fixed in 10.0.10240.2101410.0.14393.806610.0.17763.7314
Interim mitigation

Apply the relevant Microsoft security update for CVE-2025-29960 through Windows Update or WSUS. If RRAS is not required, consider disabling the service to reduce attack surface.

Recommended fix High confidence

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 | Windows 11 2

  1. 1. Identify current Windows version by running 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"'
  2. 2. Determine which version bracket your current build falls into from the affected versions list
  3. 3. Check for Windows updates via Settings > Update & Security > Windows Update
  4. 4. Apply the appropriate cumulative update for your Windows version that includes the security fix for CVE-2025-29960
  5. 5. Restart the system when prompted to complete the installation
  6. 6. Verify the installed build matches or exceeds the fixed version for your Windows release
Caveat Standard Windows update risks apply: ensure compatibility with business-critical applications and back up data before applying updates

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-29960 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-29960 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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