Security readout for executives and security teams
Plain-English summary
A memory-safety 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 user to encounter crafted HTML. Successful exploitation could expose data, alter systems, or disrupt availability. Chrome versions before 151.0.7922.72 are affected.
Executive priority
Treat this as an urgent browser-update issue because successful sandbox escape could materially increase the impact of another browser vulnerability. Accelerate deployment and verify coverage, but do not represent active exploitation as confirmed. Focus reporting on remaining installations below 151.0.7922.72.
Technical view
CVE-2026-17704 is a CWE-416 use-after-free in ANGLE. A remote attacker with prior renderer-process compromise could potentially trigger a sandbox escape through crafted HTML. The supplied CVSS 3.1 score is 9.6, reflecting network reachability, user interaction, changed scope, and potentially high confidentiality, integrity, and availability impact.
Likely exposure
Organizations running Google Chrome versions earlier than 151.0.7922.72 are potentially exposed. Risk is greatest where browser updates are delayed or unmanaged. The sources do not identify other affected products or confirm whether particular operating systems, configurations, or ANGLE backends change exposure.
Exploitation context
The provided sources do not establish active exploitation, and this CVE is not listed as KEV in the supplied record. Exploitation is described as requiring both crafted HTML and an already-compromised renderer process, so this flaw would likely function as part of a chained browser attack rather than an initial compromise.
Researcher notes
Public details in the supplied bundle are limited. The Chromium issue may contain restricted or incomplete information, so trigger mechanics, affected code paths, platform differences, and exploit reliability cannot be confirmed here. The stated renderer-compromise prerequisite is important when modeling attack chains. No exploit procedure or proof of concept is established by these sources.
Mitigation direction
- Update Google Chrome to version 151.0.7922.72 or later.
- Prioritize managed browser fleets with internet access or delayed automatic updates.
- Review Google’s release advisory for any additional vendor guidance.
- Limit use of unsupported or unmanaged Chrome installations until updated.
Validation and detection
- Inventory deployed Chrome versions across managed and unmanaged endpoints.
- Confirm every Chrome installation reports version 151.0.7922.72 or later.
- Verify update policies are functioning and failed deployments are remediated.
- Monitor vendor guidance for revised affected-version or exploitation information.
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-416: 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-17704 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/519259107CVE 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.
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.