dbcve.org
Windows 11 22h2Operating system · Microsoft

CVE-2025-24994

HIGH · 7.3 CVSS v3.1 Published 2025-03-11
Fix available
A fix is available. Upgrade to 10.0.22621.5039 / 10.0.22631.5039 or later.
See remediation →
73/100
Remediation priority · Elevated

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 Cross Device Service 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 an improper access control vulnerability in Windows Cross Device Service that allows an authorized attacker to escalate privileges locally. The vulnerability stems from insufficient validation of access permissions within the service, enabling a user with standard privileges to gain elevated access.

MitigationApply the Microsoft security update for CVE-2025-24994 immediately to all affected Windows systems. Verify that the Windows Cross Device Service is running with appropriate least-privilege configuration post-patch.

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 22h2Operating system
Affected:< 10.0.22621.5039
Windows 11 23h2Operating system
Affected:< 10.0.22631.5039
Windows 11 24h2Operating system
Affected:< 10.0.26100.3403

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/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. Verify Windows version is within affected range
    Run 'winver' or 'systeminfo' from command prompt and note the full Windows 11 build number (e.g., 10.0.22621.xxxx). Compare against affected thresholds: 22h2 builds below 10.0.22621.5039, 23h2 below 10.0.22631.5039, or 24h2 below 10.0.26100.3403 are vulnerable.
    Affected if The installed Windows 11 build number falls below any of the three version thresholds listed for the respective Windows 11 feature update.
  2. Confirm Windows Cross Device Service presence
    Open Services console (services.msc) or run 'sc query' command and look for a service related to Cross Device Service (may appear as 'Cross Device Service', 'cdsvc', or similar naming).
    Affected if The Windows Cross Device Service is installed and present on the system.
  3. Check if Cross Device Service is running
    Run 'sc query <service_name>' or check the Status column in services.msc for the Cross Device Service.
    Affected if The Cross Device Service is in a running state on the affected Windows version.
  4. Review service configuration and ACLs
    Run 'sc sdshow <service_name>' to display the security descriptor (DACL) and verify which user groups have permission to start/stop or modify the service. Check if standard users have elevated permissions.
    Affected if Standard non-admin users have permission to modify or interact with the service in ways that should be restricted.

A system is affected if it runs a vulnerable Windows 11 version (22h2, 23h2, or 24h2) below the specified build thresholds AND has the Windows Cross Device Service present and running.

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.22621.5039 / 10.0.22631.5039 / 10.0.26100.3403 or later
Fixed in 10.0.22621.503910.0.22631.503910.0.26100.3403
Interim mitigation

Apply the Microsoft security update for CVE-2025-24994 immediately to all affected Windows systems. Verify that the Windows Cross Device Service is running with appropriate least-privilege configuration post-patch.

Recommended fix High confidence

Windows 11 22h2 to version 10.0.22621.5039 or later | Windows 11 23h2 to version 10.0.22631.5039 or later | Windows 11 24h2 to version 10.0.26100.3403 or later

  1. Check current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Open Settings > Windows Update and check for updates, or manually download the update from Microsoft Update Catalog
  3. Install the appropriate security update for your Windows 11 version (KB500xxxx series containing the fix for CVE-2025-24994)
  4. Restart the system when prompted to complete the installation
  5. Verify the installation was successful by checking that the Windows version matches or exceeds: 10.0.22621.5039 for 22h2, 10.0.22631.5039 for 23h2, or 10.0.26100.3403 for 24h2

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

Fix this in Windows 11 22h2 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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