dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2025-62474

HIGH · 7.8 CVSS v3.1 Published 2025-12-09
Fix available
A fix is available. Upgrade to 10.0.14393.8688 / 10.0.17763.8146 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 access control 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

This is a local privilege escalation vulnerability in Windows Remote Access Connection Manager (RasMan service). The improper access control allows an authorized attacker to elevate their privileges from a standard user to higher privileges locally, likely by exploiting misconfigured service permissions or ACLs.

MitigationApply the Microsoft security update for CVE-2025-62474 as soon as possible. In enterprise environments, verify through patch management systems that all affected Windows systems have received the update.

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 1607Operating system
Affected:< 10.0.14393.8688
Windows 10 1809Operating system
Affected:< 10.0.17763.8146
Windows 10 21h2Operating system
Affected:< 10.0.19044.6691
Windows 10 22h2Operating system
Affected:< 10.0.19045.6691
Windows 11 23h2Operating system
Affected:< 10.0.22631.6345
Windows 11 24h2Operating system
Affected:< 10.0.26100.7392
Windows 11 25h2Operating system
Affected:< 10.0.26200.7392
Windows Server 2008Operating system
Affected:= r2

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. Check Windows version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to identify your Windows version and build number
    Affected if The build number is lower than the affected version ranges (e.g., below 10.0.14393.8688 for Windows 10 1607, below 10.0.17763.8146 for Windows 10 1809, etc.)
  2. Verify RasMan service exists
    Open Services console (services.msc) or run 'sc query rasman' to check if Remote Access Connection Manager service is installed
    Affected if The RasMan service is present on the system
  3. Check RasMan service permissions
    Run 'sc sdshow rasman' to view the security descriptor (DACL) of the RasMan service and identify if standard users have inappropriate write or full control access
    Affected if Non-admin users have Write or Full Control permissions on the RasMan service security descriptor
  4. Check for CVE-2025-62474 patch
    Run 'wmic qfe list' or check Windows Update history for security update installed around the CVE release date
    Affected if No security update for CVE-2025-62474 is installed and the Windows version falls within the affected build ranges

A system is affected if it runs a Windows version within the specified build ranges AND lacks the CVE-2025-62474 security update AND has the RasMan service with misconfigured permissions allowing standard user privilege escalation.

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.14393.8688 / 10.0.17763.8146 / 10.0.19044.6691 or later
Fixed in 10.0.14393.868810.0.17763.814610.0.19044.6691
Interim mitigation

Apply the Microsoft security update for CVE-2025-62474 as soon as possible. In enterprise environments, verify through patch management systems that all affected Windows systems have received the update.

Recommended fix High confidence

Windows 10 1607: 10.0.14393.8688 or later | Windows 10 1809: 10.0.17763.8146 or later | Windows 10 21h2: 10.0.19044.6691 or later | Windows 10 22h2: 10.0.19045.6691 or later | Windows 11 23h2: 10.0.22631.6345 or later | Windows 11 24h2: 10.0.26100.7392 or later | Windows 11 25h2: 10.0.26200.7392 or

  1. Open Windows Update Settings (Settings > Update & Security > Windows Update)
  2. Click 'Check for updates' to download and install the latest security updates
  3. Ensure the update includes the patch for CVE-2025-62474 (Windows Remote Access Connection Manager)
  4. Restart the system after the update is installed
  5. Verify the installed version matches or exceeds the fixed build version for your Windows release
Caveat Standard Windows update risks apply (potential for temporary service disruption; backup recommended for production systems)

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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