dbcve.org
Windows 11 24h2Operating system · Microsoft

CVE-2025-62572

HIGH · 7.8 CVSS v3.1 Published 2025-12-09
Fix available
A fix is available. Upgrade to 10.0.26100.7392 / 10.0.26200.7392 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
Out-of-bounds read in Application Information Services 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

Out-of-bounds read vulnerability in Windows Application Information Services enables a locally authorized attacker to read sensitive memory contents and leverage this for privilege escalation to higher integrity levels.

MitigationApply Microsoft security updates for Application Information Services when available; limit local user privileges to the minimum required and monitor for anomalous service behavior.

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 11 24h2Operating system
Affected:< 10.0.26100.7392
Windows 11 25h2Operating system
Affected:< 10.0.26200.7392
Windows Server 2025Operating system
Affected:< 10.0.26100.7392

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 and build number
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to get the exact Windows build
    Affected if Version is Windows 11 24h2, 25h2, or Server 2025 with build below 10.0.26100.7392 (for 24h2/Server 2025) or 10.0.26200.7392 (for 25h2)
  2. Confirm Windows edition matches affected products
    Verify the system is Windows 11 24h2, Windows 11 25h2, or Windows Server 2025 using 'winver' or system information
    Affected if OS is Windows 11 24h2, Windows 11 25h2, or Windows Server 2025
  3. Check Application Information Service status
    Run 'Get-Service -Name AppInfo' in PowerShell or check Services.msc for 'Application Information' service
    Affected if The AppInfo service is running or set to start (required for the vulnerability to be exploitable)
  4. Verify service is enabled for interactive users
    Check if Application Information Service allows protected applications to run with elevated privileges; review service configuration in services.msc or via 'sc qc AppInfo'
    Affected if Service is enabled and not explicitly disabled

User is affected if running Windows 11 24h2, 25h2, or Server 2025 with a build number below the specified thresholds AND the Application Information Service (AppInfo) is enabled 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.26100.7392 / 10.0.26200.7392 or later
Fixed in 10.0.26100.739210.0.26200.7392
Interim mitigation

Apply Microsoft security updates for Application Information Services when available; limit local user privileges to the minimum required and monitor for anomalous service behavior.

Recommended fix High confidence

Windows 11 24h2 build 10.0.26100.7392 | Windows 11 25h2 build 10.0.26200.7392 | Windows Server 2025 build 10.0.26100.7392

  1. Check current Windows version by running `winver` or `systeminfo` to confirm the build number
  2. Apply the relevant Windows security update from Microsoft Update Catalog (typically KB5055527 for January 2025 or subsequent relevant update)
  3. Restart the system to complete the installation
  4. Verify the update installed successfully by checking the installed updates via `Get-HotFix` or reviewing the Windows version which should now show build 10.0.26100.7392 or higher for 24h2/Server 2025, or 10.0.26200.7392 or higher for 25h2
Caveat Standard Windows security update; no expected breaking changes for typical workloads

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

Fix this in Windows 11 24h2 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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