dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-33067

HIGH · 8.4 CVSS v3.1 Published 2025-06-10
Fix available
A fix is available. Upgrade to 10.0.10240.21034 / 10.0.14393.8148 or later.
See remediation →
89/100
Remediation priority · High
No privileges 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
Improper privilege management in Windows Kernel allows an unauthorized 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 a local privilege escalation vulnerability in the Windows Kernel stemming from improper privilege management. An unauthenticated attacker with local access can exploit this flaw to elevate their privileges, potentially gaining SYSTEM-level access on the affected system.

MitigationApply the relevant Microsoft security patch for this vulnerability (refer to the associated Microsoft Security Response Center advisory for the specific KB article). Prioritize patching systems with direct user access or those exposed to untrusted users.

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 10 1507Operating system
Affected:< 10.0.10240.21034
Windows 10 1607Operating system
Affected:< 10.0.14393.8148
Windows 10 1809Operating system
Affected:< 10.0.17763.7434
Windows 10 21h2Operating system
Affected:< 10.0.19044.5965
Windows 10 22h2Operating system
Affected:< 10.0.19045.5965
Windows 11 22h2Operating system
Affected:< 10.0.22621.5472
Windows 11 23h2Operating system
Affected:< 10.0.22631.5472
Windows 11 24h2Operating system
Affected:< 10.0.26100.4270

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

CVSS:3.1/AV:L/AC:L/PR:N/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
    Open Command Prompt and run 'winver' to see the Windows version and build number, or run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' for detailed version info.
    Affected if The displayed build number falls below the threshold for your specific Windows release as listed in the affected versions.
  2. Identify exact Windows 10 release
    Run 'systeminfo' and look at the 'OS Name' field. Windows 10 releases are identified by their version numbers: 1507 (initial release), 1607 (Anniversary Update), 1809 (October 2018 Update), 21h2 (October 2021 Update), 22h2 (2022 Update).
    Affected if You are running Windows 10 and the build number is less than 10.0.10240.21034 (1507), 10.0.14393.8148 (1607), 10.0.17763.7434 (1809), 10.0.19044.5965 (21h2), or 10.0.19045.5965 (22h2) respectively.
  3. Identify exact Windows 11 release
    Run 'systeminfo' and look at the 'OS Name' field. Windows 11 releases are identified by their version numbers: 22h2 (initial release), 23h2 (2023 Update), 24h2 (2024 Update).
    Affected if You are running Windows 11 and the build number is less than 10.0.22621.5472 (22h2), 10.0.22631.5472 (23h2), or 10.0.26100.4270 (24h2) respectively.
  4. Verify build number via registry
    Open Registry Editor and navigate to 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion'. Check the 'CurrentBuild' and 'DisplayVersion' values to confirm the exact build and version.
    Affected if The 'CurrentBuild' number is lower than the threshold for your detected Windows release.

You are affected if your Windows version matches one of the listed releases AND your current build number is below the specific threshold for that release.

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.10240.21034 / 10.0.14393.8148 / 10.0.17763.7434 or later
Fixed in 10.0.10240.2103410.0.14393.814810.0.17763.7434
Interim mitigation

Apply the relevant Microsoft security patch for this vulnerability (refer to the associated Microsoft Security Response Center advisory for the specific KB article). Prioritize patching systems with direct user access or those exposed to untrusted users.

Recommended fix High confidence

Upgrade to the specific fixed build for your Windows release: 10.0.10240.21034 (Win10 1507), 10.0.14393.8148 (Win10 1607), 10.0.17763.7434 (Win10 1809), 10.0.19044.5965 (Win10 21h2), 10.0.19045.5965 (Win10 22h2), 10.0.22621.5472 (Win11 22h2), 10.0.22631.5472 (Win11 23h2), or 10.0.26100.4270 (Win11 2

  1. Identify the current Windows version and build by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine which Windows 10/11 release branch you are on (1507, 1607, 1809, 21h2, 22h2, or Windows 11 22h2/23h2/24h2)
  3. Open Settings > Windows Update and check for updates, or manually download the appropriate security update from the Microsoft Update Catalog for your specific Windows version
  4. Install the security update that includes the fix: Windows 10 1507 to build 10.0.10240.21034, Windows 10 1607 to build 10.0.14393.8148, Windows 10 1809 to build 10.0.17763.7434, Windows 10 21h2 to build 10.0.19044.5965, Windows 10 22h2 to build 10.0.19045.5965, Windows 11 22h2 to build 10.0.22621.5472, Windows 11 23h2 to build 10.0.22631.5472, or Windows 11 24h2 to build 10.0.26100.4270
  5. Restart the system after the update is installed
  6. Verify the build version matches or exceeds the fixed build for your Windows release
Caveat Standard Windows cumulative update; ensure backups of critical data and test in a staging environment before deploying broadly

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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