dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-47955

HIGH · 7.8 CVSS v3.1 Published 2025-06-10
Fix available
A fix is available. Upgrade to 10.0.10240.21014 / 10.0.14393.8066 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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
Improper privilege management in Windows Remote Access Connection Manager allows an authorized attacker to elevate privileges locally.

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

Improper privilege management in Windows Remote Access Connection Manager (RasMan) allows a local authorized attacker to elevate their privileges, potentially gaining administrative or SYSTEM-level access on the affected Windows system.

MitigationApply Microsoft security updates for CVE-2025-47955 once released; prioritize patching servers and workstations with Remote Access Connection Manager services enabled.

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.3981

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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 checks

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

  1. Identify Windows version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the installed Windows build number.
    Affected if The displayed build number falls below any of these thresholds: 10.0.10240.21014 (1507), 10.0.14393.8066 (1607), 10.0.17763.7314 (1809), 10.0.19044.5854 (21h2/22h2), 10.0.22621.5335 (11 22h2), 10.0.22631.5335 (11 23h2), or 10.0.26100.3981 (11 24h2).
  2. Locate RasMan service binary
    Run 'sc queryex RasMan' or check for 'C:\Windows\System32\rasman.exe' existence. RasMan is the Windows Remote Access Connection Manager service.
    Affected if The RasMan.exe binary exists on the system, indicating the Remote Access Connection Manager component is present.
  3. Check RasMan service status
    Run 'sc query RasMan' to query the current state of the Remote Access Connection Manager service.
    Affected if The service state shows as RUNNING, indicating the vulnerable component is active on the system.
  4. Verify RasMan binary version
    Right-click 'C:\Windows\System32\rasman.exe', select Properties, then view the File Version on the Details tab. Alternatively, run 'powershell (Get-Item C:\Windows\System32\rasman.exe).VersionInfo.FileVersion'.
    Affected if The binary version is earlier than the version corresponding to the patched build for your Windows release, or the file shows no version info indicating it may be an older build.

A system is affected if it runs a Windows version with a build number below the patched thresholds AND has the RasMan service binary present on the 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 Microsoft security updates for CVE-2025-47955 once released; prioritize patching servers and workstations with Remote Access Connection Manager services enabled.

Recommended fix High confidence

Install the latest Windows security updates from May 2025 or later (specific KB per Windows version)

  1. Open Windows Settings on the affected Windows machine
  2. Navigate to Update & Security > Windows Update
  3. Click 'Check for updates' to download and install the latest security updates
  4. Ensure the update KB containing the fix for CVE-2025-47955 is installed (check Update History for installed patches)
  5. Alternatively, manually download and install the specific security update from the Microsoft Update Catalog for your Windows version
  6. Restart the system if prompted to complete the installation
  7. Verify the installed version matches or exceeds the fixed version for your Windows release (e.g., Windows 10 22h2 should be 10.0.19045.5854 or higher)
Caveat Standard Windows update risks apply - ensure backups and compatibility testing for business-critical applications

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
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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