Security readout for executives and security teams
Plain-English summary
A memory-safety flaw in Chrome for Windows could let an attacker escape Chrome’s security sandbox after first compromising a browser renderer. Successful exploitation could expose sensitive information, alter data, or disrupt the device. The supplied CVSS score is 9.6, although Chromium classifies the issue as High severity.
Executive priority
Treat this as an urgent browser update because successful sandbox escape could materially compromise a Windows endpoint. Accelerate deployment and verify coverage, while recognizing that the supplied evidence does not show active exploitation and exploitation requires an earlier renderer compromise.
Technical view
CVE-2026-17692 is a use-after-free vulnerability (CWE-416) in Chrome’s DataTransfer component. A remote attacker with prior renderer-process compromise could potentially escape the sandbox through a crafted HTML page. The CVSS vector indicates network reachability, low complexity, user interaction, changed scope, and high confidentiality, integrity, and availability impact.
Likely exposure
Windows endpoints running Google Chrome versions earlier than 151.0.7922.72 are potentially exposed. Risk is greatest where users browse untrusted content or renderer compromise is otherwise possible. The supplied evidence does not identify other operating systems or Chromium-based products as affected.
Exploitation context
Exploitation requires a compromised renderer process and a crafted HTML page; this is therefore a sandbox-escape component of a likely exploit chain, not a standalone initial compromise. User interaction is reflected in the CVSS vector. The CVE is not listed as KEV, and the supplied sources do not establish active exploitation.
Researcher notes
The public description establishes the vulnerable component, weakness class, platform, prerequisite renderer compromise, and sandbox-escape outcome. It provides no exploit mechanics, root-cause detail, or evidence of exploitation. The affected entry naming 151.0.7922.72 conflicts superficially with the description stating versions prior to that release; the latter indicates it is the corrected boundary.
Mitigation direction
- Update Chrome on Windows to version 151.0.7922.72 or later.
- Prioritize managed Windows endpoints exposed to untrusted web content.
- Restart Chrome after updating so the corrected version is active.
- Review Google’s release guidance for any subsequent revisions or additional mitigations.
Validation and detection
- Inventory Chrome versions across Windows endpoints.
- Confirm no installed version is earlier than 151.0.7922.72.
- Verify browsers were restarted after deployment.
- Monitor update-management failures and remediate devices that remain behind.
- Check vendor guidance for changes to affected-version 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-17692 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/517350808CVE 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.