CVE-2026-17682: Integer overflow in ANGLE in Google Chrome prior to 151.0.7922.72 allowed a remote attacker who had comprom...
Integer overflow in ANGLE in Google Chrome prior to 151.0.7922.72 allowed a remote attacker who had compromised the renderer process 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 flaw in Chrome’s ANGLE graphics layer could let an attacker escape Chrome’s security sandbox after first compromising the browser’s renderer. Exploitation requires a crafted web page and user interaction. A successful attack could expose data, alter systems, or disrupt availability beyond the compromised tab.
Executive priority
Treat this as an urgent browser update because successful exploitation could cross Chrome’s sandbox and cause high-impact compromise. Accelerate deployment across exposed endpoints, while recognizing that the supplied sources do not show active exploitation and the attack requires an existing renderer compromise.
Technical view
CVE-2026-17682 is a CWE-190 integer overflow in ANGLE affecting Google Chrome before 151.0.7922.72. A remote attacker who already controls the renderer could use crafted HTML to potentially escape the sandbox. The CVSS 3.1 score is 9.6, while Chromium classifies the issue as High severity.
Likely exposure
Chrome installations running versions earlier than 151.0.7922.72 are potentially exposed when users browse attacker-controlled content. The provided evidence does not identify affected operating systems, managed-browser configurations, or other Chromium-based products, so those should not be assumed.
Exploitation context
The attack is network-accessible and requires a user to open crafted HTML, but it also depends on prior renderer compromise. The source bundle reports no CISA KEV listing and provides no evidence of active exploitation. Public exploit availability is not established by the supplied sources.
Researcher notes
The vulnerability is specifically described as an ANGLE integer overflow and potential sandbox escape. The supplied public details do not explain the vulnerable code path, affected ANGLE backends, exploit reliability, or root-cause mechanics. Avoid extending affected-product claims beyond Google Chrome without additional vendor evidence.
Mitigation direction
Update Google Chrome to version 151.0.7922.72 or later.
Prioritize systems used for web browsing, privileged administration, or sensitive-data access.
Confirm managed browser policies are successfully deploying the corrected release.
Check Google and Chromium guidance for any subsequent platform-specific instructions.
Validation and detection
Inventory Chrome versions and identify installations earlier than 151.0.7922.72.
Verify updated browsers report version 151.0.7922.72 or later.
Confirm endpoint-management deployment status and investigate update failures.
Review security telemetry for renderer compromise or unexpected browser sandbox escapes.
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-190: 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-190 · source CWE mapping
Integer Overflow or Wraparound
Integer Overflow or Wraparound represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.