dbcve.org
Windows 11 24h2Operating system · Microsoft

CVE-2025-48810

MEDIUM · 5.5 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to 10.0.26100.4652 or later.
See remediation →
57/100
Remediation priority · Elevated
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
Processor optimization removal or modification of security-critical code in Windows Secure Kernel Mode allows an authorized attacker to disclose information 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 vulnerability involves processor optimization removal or modification of security-critical code in Windows Secure Kernel Mode, allowing a local authorized attacker to potentially disclose sensitive information. The issue stems from how the secure kernel handles processor-level optimizations that may inadvertently expose security-critical code paths or timing information.

MitigationApply Microsoft security updates for Windows when available; this is a kernel-level vulnerability requiring vendor-supplied patches rather than configuration changes.

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.4652
Windows Server 2025Operating system
Affected:< 10.0.26100.4652

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
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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 build number
    Run 'winver' from command prompt or check 'HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\CurrentBuild' in registry. The build number is displayed as the Windows version.
    Affected if Build number is less than 26100.4652
  2. Confirm Windows 11 24h2 or Server 2025 edition
    Run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' or check the edition via 'winver' or 'systeminfo'. Windows 11 24h2 shows as 'Windows 11' with version '24H2'; Windows Server 2025 shows as 'Windows Server 2025'.
    Affected if The installed OS is Windows 11 version 24H2 or Windows Server 2025
  3. Verify Secure Kernel Mode is enabled
    Secure Kernel Mode is a core component of Windows Virtualization-based Security (VBS). Check if VBS is enabled by running 'msinfo32' and looking for 'Virtualization-based security' status, or via 'systeminfo' under 'Hypervisor - Code Integrity Enable'.
    Affected if VBS/Secure Kernel is present (this is default on affected versions but confirms the attack surface exists)

User is affected if running Windows 11 24H2 or Windows Server 2025 with a build number below 26100.4652, as this is a Secure Kernel Mode vulnerability that requires Microsoft-supplied patches to remediate.

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.4652 or later
Fixed in 10.0.26100.4652
Interim mitigation

Apply Microsoft security updates for Windows when available; this is a kernel-level vulnerability requiring vendor-supplied patches rather than configuration changes.

Recommended fix High confidence

Windows 11 24h2 build 10.0.26100.4652 or later; Windows Server 2025 build 10.0.26100.4652 or later

  1. Check current Windows build version by running 'winver' or 'systeminfo' in command prompt
  2. Open Windows Update by searching for 'Windows Update' in Start menu
  3. Click 'Check for updates' and install all available security updates
  4. Alternatively, manually download and install the specific KB update addressing CVE-2025-48810 from Microsoft Update Catalog
  5. Restart the computer when prompted to complete the installation
  6. Verify the build has been updated to 10.0.26100.4652 or later by running 'winver'
Caveat Standard Windows security update - no significant breaking changes expected

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

Fix this in Windows 11 24h2 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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