CVE-2026-44812
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 · uneditedInteger overflow or wraparound in Windows Win32K - GRFX allows an unauthorized attacker to execute code 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 confidenceInteger overflow in Windows Win32K graphics subsystem (GRFX) allows a local unauthenticated attacker to execute arbitrary code via crafted graphical 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 dataall versionsall versionsall versions< 10.0.14393.9234< 10.0.17763.8880< 10.0.19044.7417< 10.0.19045.7417< 10.0.22631.7219CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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.
-
Check Windows 10 build versionRun 'winver' or 'systeminfo | findstr /B /C:"OS Version"' and note the build number (e.g., 19045.xxxx)Affected if The build is less than 10.0.19045.7417 (Windows 10 22h2) or less than the threshold for your specific Windows 10 release (1607: <10.0.14393.9234, 1809: <10.0.17763.8880, 21h2: <10.0.19044.7417)
-
Check Windows 11 build versionRun 'winver' or 'systeminfo' and note the build number under 'OS Version'Affected if The build is less than 10.0.22631.7219 (Windows 11 23h2)
Your system is affected if it runs any of the Windows 10 or Windows 11 versions listed with build numbers below the specified thresholds, as the integer overflow exists in the Win32K graphics subsystem of those Windows versions.
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.14393.923410.0.17763.888010.0.19044.7417
Apply Microsoft security updates for Windows when available; prioritize patching endpoints given local code execution impact.
Windows 10 1607: 10.0.14393.9234 or later | Windows 10 1809: 10.0.17763.8880 or later | Windows 10 21h2: 10.0.19044.7417 or later | Windows 10 22h2: 10.0.19045.7417 or later | Windows 11 23h2: 10.0.22631.7219 or later
- Open Windows Settings and navigate to Update & Security > Windows Update
- Click 'Check for updates' to download and install the latest security updates
- Restart the computer after updates are installed
- Verify the installed OS version matches or exceeds the fixed version number for your Windows release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-44812 — 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-44812 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