dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2026-32215

MEDIUM · 5.5 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to 10.0.17763.8644 / 10.0.19044.7184 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
Insertion of sensitive information into log file in Windows Kernel 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

Windows Kernel vulnerability allowing an authorized local attacker to disclose sensitive information through log file insertion. The kernel improperly logs sensitive data, enabling a local authenticated attacker to read this information from log files.

MitigationApply the Microsoft security update for CVE-2026-32215 to remediate the kernel-level logging issue. Review and audit log files for any potential sensitive data exposure.

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 1809Operating system
Affected:< 10.0.17763.8644
Windows 10 21h2Operating system
Affected:< 10.0.19044.7184
Windows 10 22h2Operating system
Affected:< 10.0.19045.7184
Windows 11 23h2Operating system
Affected:< 10.0.22631.6936
Windows 11 24h2Operating system
Affected:< 10.0.26100.8246
Windows 11 25h2Operating system
Affected:< 10.0.26200.8246
Windows 11 26h1Operating system
Affected:< 10.0.28000.1836
Windows Server 2019Operating system
Affected:< 10.0.17763.8644

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 version and build number
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to display the installed Windows version and build number.
    Affected if The build number is lower than the threshold for your Windows version (17763.8644 for 1809/Server 2019, 19044.7184 for 21h2, 19045.7184 for 22h2, 22631.6936 for 23h2, 26100.8246 for 24h2, 26200.8246 for 25h2, or 28000.1836 for 26h1).
  2. Identify the specific Windows edition
    Run 'winver' or check System Properties to confirm whether the system is Windows 10 1809, 21h2, 22h2, Windows 11 23h2/24h2/25h2/26h1, or Windows Server 2019, as version thresholds differ by edition.
    Affected if The system matches any of the affected editions listed in the CVE and the build number is below the corresponding threshold.
  3. Verify if the security update is installed
    Open Settings > Windows Update > Update History, or run 'wmic qfe list' in Command Prompt to display installed hotfixes. Look for any security updates related to March 2026 or CVE-2026-32215.
    Affected if No security update addressing CVE-2026-32215 is installed and the version falls within the affected range.

A system is affected if it runs a Windows 10/11 or Windows Server 2019 version within the specified affected ranges and lacks the corresponding security update.

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.17763.8644 / 10.0.19044.7184 / 10.0.19045.7184 or later
Fixed in 10.0.17763.864410.0.19044.718410.0.19045.7184
Interim mitigation

Apply the Microsoft security update for CVE-2026-32215 to remediate the kernel-level logging issue. Review and audit log files for any potential sensitive data exposure.

Recommended fix High confidence

Windows 10 1809/Server 2019: 10.0.17763.8644 or later | Windows 10 21h2: 10.0.19044.7184 or later | Windows 10 22h2: 10.0.19045.7184 or later | Windows 11 23h2: 10.0.22631.6936 or later | Windows 11 24h2: 10.0.26100.8246 or later | Windows 11 25h2: 10.0.26200.8246 or later | Windows 11 26h1: 10.0.28

  1. Check the current Windows build version by running 'winver' or 'systeminfo' in Command Prompt
  2. Compare your current build number against the minimum fixed version for your Windows release
  3. Open Windows Update (Settings > Update & Security > Windows Update) and check for updates
  4. Install all available cumulative updates. The fix is included in the standard monthly Windows security update rollup
  5. After installation, restart your system to complete the patching process
  6. Verify the fix was applied by checking the new build version matches or exceeds: Windows 10 1809/Server 2019: 10.0.17763.8644, Windows 10 21h2: 10.0.19044.7184, Windows 10 22h2: 10.0.19045.7184, Windows 11 23h2: 10.0.22631.6936, Windows 11 24h2: 10.0.26100.8246, Windows 11 25h2: 10.0.26200.8246, Windows 11 26h1: 10.0.28000.1836
Caveat Standard Windows update requires reboot; no major functional changes expected for this security patch

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

Fix this in Windows 10 1809 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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