dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-29958

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
Use 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 · high confidence

This 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 disclose sensitive information over the network.

MitigationApply the Microsoft security update for CVE-2025-29958 to all affected Windows servers running RRAS, and verify RRAS functionality after patching.

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. Determine Windows version and build number
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the exact Windows build number
    Affected if Build number is lower than the threshold for your Windows release (10.0.10240.21014 for 1507, 10.0.14393.8066 for 1607, 10.0.17763.7314 for 1809, 10.0.19044.5854 for 21h2, 10.0.19045.5854 for 22h2, 10.0.22621.5335 for 11 22h2, 10.0.22631.5335 for 11 23h2, 10.0.26100.4061 for 11 24h2)
  2. Check if Routing and Remote Access Service (RRAS) is installed
    Open Server Manager > Manage > Add Roles and Features, or run 'Get-WindowsFeature -Name Routing' in PowerShell on Windows Server. On client Windows, check Services console for 'Routing and Remote Access' service
    Affected if RRAS role/service is installed or enabled on the system
  3. Verify RRAS is running or configured
    Run 'Get-Service RemoteAccess' or check Services.msc for the RemoteAccess service status
    Affected if RemoteAccess service is present and running, indicating RRAS is active

You are affected if your Windows build falls within the affected version ranges AND RRAS (Routing and Remote Access Service) is installed and enabled on your system.

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 Microsoft security update for CVE-2025-29958 to all affected Windows servers running RRAS, and verify RRAS functionality after patching.

Recommended fix High confidence

Upgrade to the latest cumulative security update for your specific Windows 10 or Windows 11 version that includes the fix for CVE-2025-29958 (e.g., Windows 10 22h2 build 10.0.19045.5854 or later)

  1. Identify the current Windows version and build number by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine which Windows 10 or 11 release channel you are on (e.g., 1507, 1607, 1809, 21h2, 22h2, or 11 22h2/23h2/24h2)
  3. Apply the appropriate security update from Microsoft Update Catalog or Windows Update for your specific Windows version and build
  4. Restart the system after applying the update
  5. Verify the installed version matches or exceeds the fixed build: Windows 10 1507 should be 10.0.10240.21014 or later, Windows 10 1607 should be 10.0.14393.8066 or later, Windows 10 1809 should be 10.0.17763.7314 or later, Windows 10 21h2 should be 10.0.19044.5854 or later, Windows 10 22h2 should be 10.0.19045.5854 or later, Windows 11 22h2 should be 10.0.22621.5335 or later, Windows 11 23h2 should
Caveat Standard Windows update process with minimal risk; ensure backups and test in staging if possible

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-29958 — 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-29958 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