Security readout for executives and security teams
Plain-English summary
This flaw could let an attacker break out of Chrome’s security sandbox after already compromising a browser renderer. Successful exploitation could expose sensitive data, alter systems, or disrupt operations. The attack involves a crafted web page, so prompt browser updates are warranted.
Executive priority
Treat this as an urgent browser update because successful chaining could escape Chrome’s sandbox with high confidentiality, integrity, and availability impact. Prioritize broad desktop coverage and verify completion. The evidence does not support declaring an active exploitation emergency.
Technical view
CVE-2026-17673 is a CWE-190 integer overflow in Chromium’s QUIC implementation. A remote attacker with an already-compromised renderer could potentially use crafted HTML to escape the Chrome sandbox. The supplied CVSS 3.1 score is 9.6, while Chromium classifies the issue as High severity.
Likely exposure
Chrome desktop installations earlier than 151.0.7922.72 are the stated exposure. Exploitation requires a compromised renderer and interaction with crafted HTML, indicating a multi-stage browser attack rather than a standalone initial compromise. The bundle’s affected-version entry conflicts with its description, so inventories should treat 151.0.7922.72 as the stated fixed boundary.
Exploitation context
The supplied sources do not establish active exploitation, and the CVE is not identified as being in CISA KEV. Exploitation is described as a potential sandbox escape following renderer compromise. No conclusion about public exploit availability can be drawn from this bundle.
Researcher notes
The prerequisite renderer compromise materially shapes threat modeling: this vulnerability is a sandbox-escape component suitable for an exploit chain. CVSS reports Critical at 9.6, whereas Chromium labels it High. The supplied affected array lists 151.0.7922.72, but the description says versions prior to that release; validate against vendor guidance.
Mitigation direction
- Update Chrome desktop to version 151.0.7922.72 or later.
- Prioritize managed endpoints that browse untrusted or externally supplied content.
- Review Google’s release notice and Chromium issue for subsequent vendor guidance.
- Enforce browser update policies where automatic updates are disabled or delayed.
Validation and detection
- Inventory installed Chrome versions across managed desktop endpoints.
- Confirm each installation reports version 151.0.7922.72 or later.
- Verify browser update policies are functioning and devices have restarted if required.
- Recheck exceptions, offline devices, and update failures after the deployment window.
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-190: 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-17673 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/513735177CVE 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.
Integer Overflow or Wraparound
Integer Overflow or Wraparound represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.