CVE-2025-62472
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 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 · high confidenceA local privilege escalation vulnerability exists in Windows Remote Access Connection Manager (RasMan) due to the use of an uninitialized resource. An authorized attacker with local access can exploit this to elevate their privileges to SYSTEM level, achieving full control over the affected Windows system.
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.14393.8688< 10.0.17763.8146< 10.0.19044.6691< 10.0.19045.6691< 10.0.22631.6345< 10.0.26100.7392< 10.0.26200.7392all versions= r2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Windows version build numberRun 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to obtain the full build number (e.g., 10.0.19045.xxxx)Affected if The build number falls below the threshold for your Windows release (e.g., < 10.0.19045.6691 for Windows 10 22h2)
-
Identify exact Windows releaseRun 'winver' to confirm whether the system is Windows 10 1607, 1809, 21h2, 22h2, Windows 11 23h2, 24h2, 25h2, or Windows Server 2008 R2Affected if The system is any affected version listed in the CVE (Windows 10 1607/1809/21h2/22h2, Windows 11 23h2/24h2/25h2, or Windows Server 2008 R2)
-
Verify RasMan service presenceRun 'Get-Service -Name RasMan' in PowerShell or 'sc query RasMan' to check if the Remote Access Connection Manager service existsAffected if The RasMan service is present on the system (this is the vulnerable component)
-
Confirm service statusRun 'Get-Service -Name RasMan | Select-Object Status' to check if the service is runningAffected if The RasMan service is running (required for exploitation, though the vulnerability exists in the service binary regardless of state)
You are affected if your Windows version matches one of the affected releases AND the build number is below the specified threshold for that release, AND the RasMan service is present on the system.
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.14393.868810.0.17763.814610.0.19044.6691
Apply the Microsoft security update addressing CVE-2025-62472 through Windows Update or the relevant KB patch. Verify the Remote Access Connection Manager service functions normally after patching.
Windows 10 1607: 10.0.14393.8688 | Windows 10 1809: 10.0.17763.8146 | Windows 10 21h2: 10.0.19044.6691 | Windows 10 22h2: 10.0.19045.6691 | Windows 11 23h2: 10.0.22631.6345 | Windows 11 24h2: 10.0.26100.7392 | Windows 11 25h2: 10.0.26200.7392 | Windows Server 2008 R2: migrate to supported Windows Se
- Identify the current Windows build version by running 'winver' or 'systeminfo' in Command Prompt
- Open Windows Settings > Update & Security > Windows Update
- Click 'Check for updates' to download and install the latest cumulative update containing the security fix
- If automatic updates are unavailable, manually download the specific KB update from the Microsoft Update Catalog (catalog.update.microsoft.com) matching your Windows version
- After installing the update, restart the system to apply the changes
- Verify the fix by confirming the build number matches or exceeds the fixed version for your Windows release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing3.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,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-62472 — 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-62472 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