Security readout for executives and security teams
Plain-English summary
A malicious webpage could abuse a memory-writing flaw in Chrome’s ANGLE graphics layer after the browser renderer was already compromised. Successful exploitation could let an attacker escape Chrome’s sandbox and potentially affect the underlying system. Google identifies the Chromium severity as High, while the supplied CVSS assessment is 9.6 Critical.
Executive priority
Treat this as an urgent browser update because sandbox escape can turn a browser compromise into broader system impact. Accelerate deployment across internet-facing user endpoints, while recognizing that exploitation requires a separate renderer compromise and is not reported as active.
Technical view
CVE-2026-17675 is a CWE-787 out-of-bounds write in ANGLE affecting Google Chrome versions before 151.0.7922.72. A remote attacker with prior renderer-process compromise could use crafted HTML to attempt sandbox escape. The renderer-compromise prerequisite indicates this is likely a chained vulnerability rather than a standalone initial-compromise path.
Likely exposure
Endpoints running Chrome versions earlier than 151.0.7922.72 are potentially exposed when users browse untrusted content. Exposure depends on an attacker first compromising the renderer process. The supplied evidence does not identify other Chromium-based browsers or products as affected.
Exploitation context
The supplied sources do not report active exploitation, and the CVE is not listed as KEV in the bundle. Exploitation requires user interaction with crafted HTML and an already-compromised renderer. Public exploit availability and attack-chain details are not established by the provided evidence.
Researcher notes
The available record identifies the vulnerable component, write primitive, crafted-HTML vector, and sandbox-escape impact, but provides limited root-cause detail. Do not infer exploitability beyond the stated renderer-compromise prerequisite. The affected-version entry is ambiguous alone; the description clearly states that versions before 151.0.7922.72 are affected.
Mitigation direction
- Update Google Chrome to version 151.0.7922.72 or later.
- Prioritize managed endpoints that browse external or untrusted websites.
- Enforce browser update policies and investigate devices that cannot receive the current release.
- Check Google’s release guidance for any subsequent platform-specific instructions.
Validation and detection
- Inventory Chrome versions and identify installations earlier than 151.0.7922.72.
- Confirm the updated browser version after restarting Chrome on each managed platform.
- Verify enterprise update policies are enabled and reporting successful installation.
- Monitor vendor and government advisories for changes in exploitation status.
Public sources used
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-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.
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-17675 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
- Critical
- CVSS
- 9.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
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:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H2.86CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.6CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
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
- https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.htmlCVE reference, Chrome
- https://issues.chromium.org/issues/513920258CVE reference, Chrome
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.
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.