CVE-2026-17691: Out of bounds write in ANGLE in Google Chrome on Windows prior to 151.0.7922.72 allowed a remote attacker t...
Out of bounds write in ANGLE in Google Chrome on Windows prior to 151.0.7922.72 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)
Security readout for executives and security teams
Plain-English summary
A malicious webpage could abuse a memory-safety flaw in Chrome’s ANGLE graphics layer on Windows and potentially escape the browser sandbox. Successful exploitation could expose data, alter systems, or disrupt operations. The supplied CVSS score is 9.6, while Chromium classifies the flaw as High severity.
Executive priority
Treat as an urgent browser-update issue because exposure requires only malicious web content and may lead to sandbox escape with broad impact. Accelerate Windows Chrome patching and verify completion. Current evidence does not show active exploitation, but the low-complexity remote attack path warrants prompt action.
Technical view
CVE-2026-17691 is a CWE-787 out-of-bounds write in ANGLE affecting Google Chrome on Windows before 151.0.7922.72. A remote attacker could trigger it through crafted HTML. The CVSS vector indicates network delivery, low complexity, no privileges, required user interaction, changed scope, and high confidentiality, integrity, and availability impact.
Likely exposure
Windows endpoints running Chrome versions earlier than 151.0.7922.72 are potentially exposed when users visit attacker-controlled or compromised webpages. The supplied evidence does not identify other operating systems, Chromium-based browsers, or affected ANGLE deployments, so their status should not be assumed.
Exploitation context
The sources describe remote exploitation through crafted HTML and a potential sandbox escape. User interaction is required, consistent with visiting or opening malicious web content. The CVE is not listed as KEV in the supplied bundle, and no cited source establishes active exploitation.
Researcher notes
The supplied record identifies the vulnerable component and impact but provides no root-cause detail, proof of exploitation, or exploit telemetry. The Chromium issue may restrict technical details. The affected-version array is ambiguous because it lists 151.0.7922.72, while the description clearly states versions prior to that release are affected.
Mitigation direction
Update Chrome on Windows to 151.0.7922.72 or later.
Prioritize managed endpoints that browse untrusted or internet-hosted content.
Enforce browser update policies and restart Chrome to activate the updated build.
Check current Google guidance for any additional mitigations or revised affected-product information.
Validation and detection
Inventory Chrome versions across all Windows endpoints.
Confirm no Windows installation remains below 151.0.7922.72.
Verify Chrome restarted after updating and reports the expected version.
Review update-management failures and isolate persistently outdated endpoints.
Monitor vendor and KEV sources for exploitation-status changes.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · low confidence lookup
CWE-787: 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.
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.
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.
1CVSS vectors
3Timeline events
1ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-787 · source CWE mapping
Out-of-bounds Write
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.