CVE-2026-32218
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 · uneditedInsertion 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 confidenceWindows Kernel contains a vulnerability where sensitive information is inadvertently written to log files, allowing a local authorized attacker to access information they should not have access to. This is an information disclosure flaw in the kernel's logging mechanisms.
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.19044.7184< 10.0.19045.7184< 10.0.22631.6936< 10.0.26100.8246< 10.0.26200.8246< 10.0.28000.1836< 10.0.20348.5020< 10.0.25398.2274CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Windows version against affected rangesRun 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to obtain the build number. Compare against: Windows 10 21h2 (<10.0.19044.7184), 10 22h2 (<10.0.19045.7184), Windows 11 23h2 (<10.0.22631.6936), 11 24h2 (<10.0.26100.8246), 11 25h2 (<10.0.26200.8246), 11 26h1 (<10.0.28000.1836), Server 2022 (<10.0.20348.5020), Server 2022 23h2 (<10.0.25398.2274)Affected if The installed Windows build number falls below the specified threshold for your Windows version
-
Identify kernel log files present on the systemInspect common Windows log directories: %SystemRoot%\System32\winevt\Logs (Event Viewer logs), %SystemRoot%\Debug, %SystemRoot%\Logs, and any configured kernel debug logs. Use 'Get-ChildItem -Path $env:SystemRoot -Recurse -Filter "*.log" -ErrorAction SilentlyContinue' with appropriate permissions to enumerate log files.Affected if Kernel-related log files exist on the system, creating potential targets for the information disclosure
-
Verify log file access permissionsRun 'icacls <log_file_path>' on suspected kernel log files to inspect ACLs. Check for overly permissive settings that allow standard users or non-privileged accounts to read sensitive log files.Affected if Standard user accounts or unauthorized groups have read access to kernel log files that may contain sensitive information
-
Audit recent log file access eventsUse Windows Event Viewer to search Security logs for Event ID 4663 (Object Access) or enable Advanced Audit Policy for 'File System' and review access to log directories. Alternatively, run 'Get-WinEvent -FilterHashtable @{LogName='Security';ID=4663} -MaxEvents 50' to review recent accesses.Affected if Unusual or unauthorized access to kernel log files is recorded, indicating active exploitation attempts
A user is affected if their Windows version is below the specified build threshold AND kernel log files exist on the system that could contain inadvertently disclosed sensitive information.
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.19044.718410.0.19045.718410.0.20348.5020
Apply the appropriate Microsoft security update for Windows Kernel when released. Ensure proper access controls on system log files and monitor for unauthorized access.
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 | Windows Server 2022: 10.0.20348.5020 | Windows Server 2022 23h2: 10.0.25398.2274
- Apply the latest Windows security updates from Windows Update or your organization's patch management system
- Verify the update was installed by checking the Windows version/build number matches or exceeds the fixed version for your Windows edition
- Confirm the update is listed in Windows Update History under security updates
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32218 — 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-2026-32218 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