Security readout for executives and security teams
Plain-English summary
A person who already has limited access to an affected Windows device could exploit a Win32K graphics race condition to gain higher privileges. Successful exploitation could enable complete compromise of that device’s confidentiality, integrity, and availability. The flaw is serious but requires local access and difficult timing conditions.
Executive priority
Treat this as a high-priority patching issue, especially on systems accessible to lower-trust users or accounts. It is not presented as remotely exploitable or actively exploited, so prioritize through risk-based patching rather than emergency internet-edge containment.
Technical view
CVE-2026-33839 is a CWE-362 synchronization flaw in Windows Win32K-GRFX. Its CVSS 3.1 score is 7.0: local attack vector, high attack complexity, low privileges, no user interaction, unchanged scope, and high impact across confidentiality, integrity, and availability.
Likely exposure
Exposure includes the listed Windows 10, Windows 11, Windows Server 2019, 2022, 2022 23H2, and 2025 releases, including specified Server Core installations. Organizations should compare exact installed builds and update levels with Microsoft’s advisory; the supplied version entries alone do not establish whether an endpoint remains vulnerable.
Exploitation context
The attacker must already be authorized with low privileges on the target and execute locally. High attack complexity suggests exploitation depends on winning a race condition. The bundle states KEV is false and provides no evidence of active exploitation; this does not prove exploitation is absent.
Researcher notes
The source bundle identifies improper synchronization over a shared resource in Win32K-GRFX but provides no triggering sequence, affected code path, or exploitation telemetry. Validation should focus on Microsoft-defined build and update applicability. Avoid inferring exploit maturity from the CVSS score or race-condition classification.
Mitigation direction
- Review Microsoft’s CVE advisory and deploy the applicable security update.
- Prioritize shared workstations, multi-user servers, and systems where untrusted users have local access.
- Restrict unnecessary local logon and code-execution access while updates are pending.
- Follow vendor guidance for unsupported or otherwise unpatchable Windows releases.
Validation and detection
- Inventory affected Windows editions, builds, installation types, and current update levels.
- Compare each system’s update status with Microsoft’s CVE advisory.
- Confirm successful update installation through endpoint management and deployment reporting.
- Investigate update failures and systems excluded from normal patching workflows.
- Monitor for unexpected privilege elevation, recognizing that telemetry does not confirm patch status.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-362: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-33839 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C15.9microsoftVulnerability scoring details
Base CVSS 3.1 score
7HighVector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- Win32k Elevation of Privilege VulnerabilityCVE reference, microsoft · vendor-advisory, patch
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.