Security readout for executives and security teams
Plain-English summary
A memory-safety flaw in Chrome on ChromeOS could let an attacker break out of the browser sandbox through a crafted webpage, but only after compromising the renderer process. Successful exploitation could expose data, alter systems, or disrupt availability. Chrome versions before 151.0.7922.72 are affected.
Executive priority
Treat as an urgent ChromeOS patching priority because sandbox escape can convert a browser compromise into broader system impact. Rapidly identify outdated devices and enforce the corrected release, while noting that active exploitation is not established by the supplied evidence.
Technical view
CVE-2026-17680 is a CWE-122 heap buffer overflow in Chrome’s Color component on ChromeOS. A remote attacker with prior renderer-process compromise could potentially trigger a sandbox escape using crafted HTML. CVSS 3.1 is 9.6, while Chromium classifies the vulnerability as High.
Likely exposure
Organizations using ChromeOS with Chrome versions earlier than 151.0.7922.72 are potentially exposed. Risk depends on users reaching attacker-controlled content and the attacker first compromising the renderer. The bundle does not identify other operating systems or products as affected.
Exploitation context
The supplied record is not in CISA KEV and provides no evidence of active exploitation. Exploitation requires user interaction, crafted HTML, and an already-compromised renderer process. The flaw could then enable a sandbox escape with high confidentiality, integrity, and availability impact.
Researcher notes
The key exploit-chain condition is prior renderer compromise; this is not described as a standalone initial-access vulnerability. Public details establish the Color component, heap overflow class, crafted-HTML vector, and potential sandbox escape. Root cause, affected code paths, and exploit reliability are not available in the bundle.
Mitigation direction
- Update Chrome on ChromeOS to version 151.0.7922.72 or later.
- Prioritize managed ChromeOS fleets exposed to untrusted web content.
- Restrict risky browsing on unpatched devices until updates are confirmed.
- Review Google and Chromium guidance for any additional mitigations.
Validation and detection
- Inventory Chrome versions across all managed ChromeOS devices.
- Confirm no ChromeOS device runs a version earlier than 151.0.7922.72.
- Verify update policies successfully deployed the corrected release.
- Recheck newly enrolled or intermittently connected devices for outdated versions.
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-122: 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-17680 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/516486611CVE 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.
Heap-based Buffer Overflow
Heap-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.