CVE-2026-35419
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 · uneditedOut-of-bounds read in Windows DWM Core Library 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 confidenceAn out-of-bounds read vulnerability exists in the Windows Desktop Window Manager (DWM) Core Library. By exploiting this flaw, a locally authenticated attacker with authorized access can read unintended memory contents, potentially exposing sensitive information. The vulnerability stems from improper bounds checking when the DWM Core Library processes certain operations.
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.26100.8390< 10.0.26200.8390< 10.0.28000.2113< 10.0.26100.32772CVSS 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 build versionRun 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to get the exact Windows build numberAffected if The build number is below 10.0.26100.8390 for Windows 11 24h2/Server 2025, below 10.0.26200.8390 for Windows 11 25h2, or below 10.0.28000.2113 for Windows 11 26h1
-
Verify DWM process is runningOpen Task Manager or run 'tasklist | findstr dwm.exe' to confirm the Desktop Window Manager (dwm.exe) process is activeAffected if DWM is running and the Windows version falls within the affected build ranges
-
Check DWM Core Library file versionRight-click dwm.exe in C:\Windows\System32, select Properties, and view the Details tab for version information, or run 'powershell (Get-Item C:\Windows\System32\dwm.exe).VersionInfo'Affected if The file version is lower than the version corresponding to the fixed builds (8390 for 24h2/Server 2025, 8390 for 25h2, 2113 for 26h1)
If the Windows build version is below the specified thresholds AND DWM is running, the environment is likely affected by this vulnerability.
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.26100.839010.0.26100.3277210.0.26200.8390
Apply the relevant Microsoft Windows security update for CVE-2026-35419 once released. Until the patch is available, limit local user privileges and monitor for suspicious processes interacting with the DWM Core Library (dwm.exe).
Windows 11 24h2: build 10.0.26100.8390+ | Windows 11 25h2: build 10.0.26200.8390+ | Windows 11 26h1: build 10.0.28000.2113+ | Windows Server 2025: build 10.0.26100.32772+
- Open Windows Settings and navigate to Windows Update
- Click 'Check for updates' to download and install the latest security updates
- Alternatively, manually download the update from the Microsoft Update Catalog (catalog.update.microsoft.com) using the specific KB number for your Windows version
- Restart the computer after the update is installed
- Verify the installed version matches or exceeds the fixed build number: Windows 11 24h2 should be 10.0.26100.8390 or later, Windows 11 25h2 should be 10.0.26200.8390 or later, Windows 11 26h1 should be 10.0.28000.2113 or later, Windows Server 2025 should be 10.0.26100.32772 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35419 — 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-35419 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