Security readout for executives and security teams
Plain-English summary
A serious Chrome flaw could let an attacker break out of the browser sandbox after first compromising Chrome's renderer through a crafted web page. Successful exploitation could expose data, alter systems, or disrupt availability. Google identifies Chrome versions before 151.0.7922.72 as vulnerable.
Executive priority
Treat this as an urgent browser-update requirement because sandbox escape can turn a browser compromise into broader system impact. Prioritize high-risk browsing populations and verify fleet-wide completion. Current sources do not establish active exploitation.
Technical view
CVE-2026-17687 is a CWE-843 type-confusion vulnerability in ANGLE. A remote attacker with an already-compromised renderer could potentially escape Chrome's sandbox using crafted HTML. The CVSS 3.1 score is 9.6, while Chromium rates the issue High. User interaction is required, and renderer compromise is a prerequisite.
Likely exposure
Endpoints running Google Chrome versions earlier than 151.0.7922.72 are potentially exposed. Practical exploitation requires a user to encounter crafted HTML and the attacker to have already compromised the renderer. The supplied evidence does not identify other affected products.
Exploitation context
The supplied bundle reports no CISA KEV listing and provides no evidence of active exploitation. This is a potential sandbox-escape stage rather than a standalone initial compromise: an attacker must first control the renderer. Public technical details in the supplied evidence are limited.
Researcher notes
The vulnerability is described only as ANGLE type confusion enabling a potential sandbox escape after renderer compromise. The supplied sources do not disclose the faulty component path, trigger conditions, exploit reliability, or indicators of compromise. Avoid inferring a complete exploit chain from the CVSS score alone.
Mitigation direction
- Upgrade Google Chrome to version 151.0.7922.72 or later through the vendor's stable channel.
- Confirm automatic browser updates are enabled and users restart Chrome to complete installation.
- Check Google's release and Chromium issue pages for revised guidance or affected-version clarification.
Validation and detection
- Inventory installed Chrome versions and flag every instance earlier than 151.0.7922.72.
- Verify Chrome reports version 151.0.7922.72 or later after restart.
- Re-scan managed endpoints to identify devices that missed or failed the update.
- Review browser telemetry for unexpected renderer crashes or sandbox-related anomalies, without treating them as proof of exploitation.
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-843: 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-17687 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/516985726CVE 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.
Access of Resource Using Incompatible Type ('Type Confusion')
Access of Resource Using Incompatible Type ('Type Confusion') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.