CVE-2025-53155
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 · uneditedHeap-based buffer overflow in Windows Hyper-V 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 confidenceA heap-based buffer overflow vulnerability exists in Windows Hyper-V that allows an authenticated local attacker to elevate privileges to a higher level. The vulnerability is present in the Hyper-V hypervisor component and could allow an attacker with existing local access to gain elevated system privileges.
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.10240.21100< 10.0.14393.8330< 10.0.17763.7678< 10.0.19044.6216< 10.0.19045.6216< 10.0.22621.5768< 10.0.22631.5768< 10.0.26100.4851CVSS 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.
-
Confirm Hyper-V is enabledRun 'Get-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V' in PowerShell with admin rights, or check via 'systeminfo' and look for Hyper-V requirementsAffected if Hyper-V is not present or not enabled, the vulnerability does not apply because it exists in the Hyper-V hypervisor component
-
Determine installed Windows versionRun 'winver' or 'systeminfo' and note the full version number shown (e.g., 10.0.19045.6216)Affected if The displayed version falls below any of the vulnerable thresholds: 10.0.10240.21100 (1507), 10.0.14393.8330 (1607), 10.0.17763.7678 (1809), 10.0.19044.6216 (21h2), 10.0.19045.6216 (22h2), 10.0.22621.5768 (22h2 Win11), 10.0.22631.5768 (23h2 Win11), or 10.0.26100.4851 (24h2 Win11)
-
Verify attacker has local accessReview local user accounts and permissions on the system; confirm the attacker already has authenticated local access (this is a privilege escalation, not an initial access vector)Affected if The attacker would need existing authenticated local access to the Hyper-V host to exploit this heap-based buffer overflow for privilege elevation
You are affected if Hyper-V is enabled on your Windows host and your installed Windows version is lower than the corresponding patch threshold for your Windows release line.
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.10240.2110010.0.14393.833010.0.17763.7678
Apply Microsoft security updates for Windows Hyper-V as they become available; given this is a privilege escalation issue, prioritize patching Hyper-V hosts in high-security environments and ensure proper access controls are maintained until patches are deployed.
Windows 10 1507 to 10.0.10240.21100 | Windows 10 1607 to 10.0.14393.8330 | Windows 10 1809 to 10.0.17763.7678 | Windows 10 21h2 to 10.0.19044.6216 | Windows 10 22h2 to 10.0.19045.6216 | Windows 11 22h2 to 10.0.22621.5768 | Windows 11 23h2 to 10.0.22631.5768 | Windows 11 24h2 to 10.0.26100.4851
- Identify the current Windows version and build number by running 'winver' or 'systeminfo'
- Determine which Windows 10 or 11 version and build you are running from the affected versions list
- Apply the corresponding security update for your specific Windows version from Windows Update or Microsoft Update Catalog
- For Windows 10 1507 (build < 10.0.10240.21100): Update to build 10.0.10240.21100 or later
- For Windows 10 1607 (build < 10.0.14393.8330): Update to build 10.0.14393.8330 or later
- For Windows 10 1809 (build < 10.0.17763.7678): Update to build 10.0.17763.7678 or later
- For Windows 10 21h2 (build < 10.0.19044.6216): Update to build 10.0.19044.6216 or later
- For Windows 10 22h2 (build < 10.0.19045.6216): Update to build 10.0.19045.6216 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,320.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-53155 — 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-53155 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