Security readout for executives and security teams
Plain-English summary
A memory-handling flaw in Windows GDI could let an attacker run code after a user interacts with malicious content. Successful exploitation could expose data, alter systems, or cause disruption. The supplied scoring describes a local attack path requiring user interaction, despite the advisory title using “Remote Code Execution.”
Executive priority
Treat as an expedited high-priority patching issue because successful exploitation could compromise data and system integrity. Prioritize exposed user endpoints and important servers, while validating applicability through Microsoft’s advisory. Emergency incident response is not justified by the supplied evidence alone because active exploitation is not established.
Technical view
CVE-2026-35421 is a heap-based buffer overflow (CWE-122) in Windows GDI. CVSS 3.1 is 7.8: local access vector, low complexity, no privileges required, and user interaction required. Successful exploitation may completely affect confidentiality, integrity, and availability. The bundle does not identify the triggering format, vulnerable function, or execution context.
Likely exposure
Potential exposure spans listed Windows 10 releases, Windows 11 23H2 through 26H1, and Windows Server 2012 through 2025, including several Server Core installations. Systems should not be classified as vulnerable solely from the base version numbers; confirm applicable update and build status against Microsoft’s advisory.
Exploitation context
The bundle provides no evidence of active exploitation, and the CVE is not marked as included in CISA KEV. Exploitation requires user interaction and uses a local attack vector according to the supplied CVSS vector. No public exploit, attack chain, indicators, or observed campaign details are provided.
Researcher notes
The title suggests remote code execution, but the supplied description and CVSS vector specify local execution with required user interaction. The sources provided here do not explain delivery mechanics, affected GDI operations, execution privileges, exact patched builds, KB mappings, proof-of-concept availability, or detection indicators. Those details require confirmation from Microsoft’s live advisory.
Mitigation direction
- Review Microsoft’s advisory and deploy the applicable security update for every affected Windows release.
- Prioritize systems whose users regularly interact with untrusted content.
- Restrict exposure of systems that cannot be updated while awaiting Microsoft-supported remediation.
- Follow Microsoft guidance for any release-specific prerequisites, mitigations, or servicing requirements.
Validation and detection
- Inventory the listed Windows client and server releases across the environment.
- Map each device’s edition, build, and patch status to Microsoft’s advisory.
- Verify applicable security updates installed successfully and survived reboot where required.
- Rescan patched assets and investigate update failures or unsupported operating systems.
- Monitor security reporting for exploitation evidence or indicators not present in this bundle.
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-122: 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 lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-35421 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.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C1.85.9microsoftVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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
- Windows GDI Remote Code Execution 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.
Heap-based Buffer Overflow
Heap-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.