CVE-2026-17695: Inappropriate implementation in ANGLE in Google Chrome on Mac prior to 151.0.7922.72 allowed a remote attac...
Inappropriate implementation in ANGLE in Google Chrome on Mac 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 website could exploit a flaw in Chrome’s ANGLE graphics layer on macOS and potentially escape the browser sandbox. Successful exploitation requires a user to open crafted web content but needs no account or prior access. The supplied CVSS score is 9.6, while Chromium classifies the issue as High severity.
Executive priority
Treat this as an urgent macOS browser update because untrusted web content could potentially escape Chrome’s sandbox. Expedite deployment and verify completion, especially on privileged or sensitive endpoints. Current evidence does not establish active exploitation, so communicate urgency without presenting the issue as an ongoing campaign.
Technical view
CVE-2026-17695 is an inappropriate ANGLE implementation affecting Google Chrome for Mac before 151.0.7922.72. Crafted HTML may enable a remote attacker to cross the Chrome sandbox boundary, potentially compromising confidentiality, integrity, and availability. The record maps the weakness to CWE-693 and reports network reachability, low complexity, no privileges, and required user interaction.
Likely exposure
Mac systems 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-derived browsers, or affected ANGLE deployments, so their exposure should not be assumed.
Exploitation context
The source bundle describes exploitation through a crafted HTML page and potential sandbox escape. It does not report observed attacks, public exploit availability, or inclusion in CISA KEV; KEV status is false. Active exploitation therefore cannot be claimed from the supplied evidence.
Researcher notes
The public record provides limited root-cause detail beyond an inappropriate ANGLE implementation and CWE-693 classification. It does not disclose the vulnerable code path, exploitation reliability, prerequisites beyond crafted HTML, or indicators of compromise. Researchers should rely on authorized vendor disclosures and avoid inferring cross-platform or downstream-browser impact.
Mitigation direction
Update Chrome on macOS to version 151.0.7922.72 or later.
Restart Chrome after updating so the corrected version is active.
Prioritize managed Macs used for web browsing or access to sensitive systems.
Check Google’s release guidance for any additional vendor-recommended actions.
Validation and detection
Inventory Chrome versions across all managed macOS endpoints.
Confirm no managed Mac remains below Chrome 151.0.7922.72.
Verify users restarted Chrome and the running version reflects the update.
Review update-management failures and remediate devices that missed deployment.
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-693: 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-693 · source CWE mapping
Protection Mechanism Failure
Protection Mechanism Failure represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.