dbcve.org
Windows 11 24h2Operating system · Microsoft

CVE-2025-48002

MEDIUM · 5.7 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to 10.0.26100.4652 or later.
See remediation →
59/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
Integer overflow or wraparound in Windows Hyper-V allows an authorized attacker to disclose information over an adjacent network.

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

Integer overflow or wraparound vulnerability in Windows Hyper-V allows an authenticated attacker on an adjacent network to trigger the overflow, potentially disclosing sensitive information from the hypervisor or virtual machines.

MitigationApply Microsoft security updates for Windows Hyper-V when available. Restrict network access to Hyper-V hosts to trusted administrative segments to reduce adjacent network attack surface.

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
Adjacent
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:A/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 version and build number
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to see the installed Windows version. Look for Windows 11 version 24h2 or Windows Server 2025.
    Affected if The installed version shows Windows 11 24h2 or Windows Server 2025 with a build number lower than 10.0.26100.4652.
  2. Verify Hyper-V role is enabled
    Run 'Get-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V' in PowerShell (for Windows 11) or 'Get-WindowsFeature -Name Hyper-V' for Windows Server 2025 to check if the Hyper-V role is installed and enabled.
    Affected if The Hyper-V role is installed and enabled on the affected Windows version.
  3. Confirm specific build version
    Run 'winver' to see the exact build number displayed, or run 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuild' to retrieve the build number programmatically.
    Affected if The CurrentBuild value is less than 26100, or equals 26100 but the full version (like 10.0.26100.xxxx) is below 10.0.26100.4652.
  4. Check adjacent network exposure
    Review network configuration to determine if the Hyper-V host is accessible from untrusted adjacent networks. Check firewall rules and network segmentation settings that govern access to the hypervisor.
    Affected if The Hyper-V host has accessible network interfaces on untrusted or insufficiently segmented networks.

You are affected if you are running Windows 11 24h2 or Windows Server 2025 with a build below 10.0.26100.4652, Hyper-V is enabled, and the host is reachable from adjacent networks.

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 Hyper-V when available. Restrict network access to Hyper-V hosts to trusted administrative segments to reduce adjacent network attack surface.

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. Open Settings > Windows Update and check for available updates
  2. Install any pending security updates for Windows 11 24h2 or Windows Server 2025
  3. Alternatively, run 'winver' to verify the current build version
  4. Ensure the installed version is 10.0.26100.4652 or higher
  5. If the update is not available yet, monitor Microsoft Update Catalog for KB5055523 or subsequent security updates
Caveat Standard Windows security update; no major 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
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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