Security readout for executives and security teams
Plain-English summary
A cryptographic flaw in Chrome Enterprise can let an attacker who controls or intercepts network traffic bypass access controls. Successful exploitation could expose or alter sensitive information without user interaction. The available record describes versions before 151.0.7922.72 as vulnerable.
Executive priority
Treat this as an urgent browser-update issue because compromise could expose or alter sensitive data without user action. Accelerate enterprise rollout and verify completion, while recognizing that the supplied sources do not establish active exploitation.
Technical view
CVE-2026-17666 is a CWE-325 cryptographic weakness affecting Google Chrome Enterprise before 151.0.7922.72. A privileged network attacker can send malicious traffic to bypass discretionary access control. CVSS 3.1 is 9.1, reflecting network reachability, low complexity, no privileges, no user interaction, and high confidentiality and integrity impact.
Likely exposure
Organizations using Chrome Enterprise versions earlier than 151.0.7922.72 are potentially exposed, particularly on networks where attackers could intercept or manipulate traffic. The sources do not identify affected operating systems, configurations, or prerequisites beyond the privileged network position.
Exploitation context
The supplied record is not in CISA KEV and provides no evidence of active exploitation. Exploitation requires a privileged network position, but reportedly needs no victim interaction or existing application privileges. Public exploit availability is not established by the supplied sources.
Researcher notes
The public description is limited and does not identify the affected cryptographic mechanism, Enterprise component, attack prerequisites beyond network position, or observable indicators. The CVE’s critical CVSS rating differs from Chromium’s High severity label. The wording indicates 151.0.7922.72 is the corrected boundary, although the structured affected entry is ambiguous.
Mitigation direction
- Update Chrome Enterprise to 151.0.7922.72 or later, following Google’s release guidance.
- Prioritize devices operating on untrusted, shared, or potentially compromised networks.
- Apply network protections that reduce unauthorized traffic interception while updates are deployed.
- Review Google and Chromium advisories for additional mitigations or revised affected-version information.
Validation and detection
- Inventory Chrome Enterprise versions and identify installations earlier than 151.0.7922.72.
- Confirm managed devices successfully received and activated the updated browser version.
- Review management-console data for devices failing, deferring, or blocking browser updates.
- Investigate relevant network-security alerts for suspicious interception or access-control bypass indicators.
- Recheck Google’s release notice and Chromium issue for updated technical details.
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-325: 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 lookupCVE-2026-17666 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.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
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:N/S:U/C:H/I:H/A:N3.95.2CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.1CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
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/511761758CVE 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.
Missing Cryptographic Step
Missing Cryptographic Step represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.