CVE-2026-17991: Insufficient validation of untrusted input in AI in Google Chrome prior to 151.0.7922.72 allowed a remote a...
Insufficient validation of untrusted input in AI in Google Chrome prior to 151.0.7922.72 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Low)
Security readout for executives and security teams
Plain-English summary
CVE-2026-17991 is a Chrome sandbox-escape vulnerability involving insufficient validation in an AI component. A remote attacker could potentially escape Chrome’s security sandbox through a crafted webpage, but only after compromising the renderer process. The supplied CVSS score is 9.6, while Chromium rates the issue Low, creating a material severity discrepancy.
Executive priority
Treat remediation as high priority because a successful sandbox escape could materially increase the impact of another browser vulnerability. Accelerate Chrome updates across managed endpoints, while recognizing that exploitation requires a prior renderer compromise. Do not characterize this issue as actively exploited based on the supplied evidence.
Technical view
In Chrome versions before 151.0.7922.72, insufficient validation of untrusted input in an AI component could allow an attacker controlling a compromised renderer to potentially cross the sandbox boundary through crafted HTML. The issue is classified as CWE-20. The sources do not establish a standalone renderer compromise path or confirm reliable sandbox escape.
Likely exposure
Chrome installations older than 151.0.7922.72 are potentially exposed. Practical risk depends on an attacker first compromising the renderer and inducing interaction with crafted web content. The supplied evidence does not identify affected operating systems, enterprise configurations, or other Chromium-based products, so exposure should not be extended beyond Google Chrome without vendor confirmation.
Exploitation context
The supplied record does not report active exploitation, and the CVE is not listed as KEV in the bundle. Exploitation requires a compromised renderer, crafted HTML, and user interaction. This makes the flaw a likely component of a chained browser attack rather than a complete initial-compromise technique by itself.
Researcher notes
The supplied CVSS 9.6 conflicts sharply with Chromium’s Low severity rating. Researchers should preserve both assessments and avoid assuming the sandbox escape is independently exploitable. The public description establishes CWE-20 and a renderer-compromise prerequisite but provides no root-cause detail, exploit reliability, affected-platform breakdown, or evidence of exploitation.
Mitigation direction
Update Google Chrome to version 151.0.7922.72 or later.
Prioritize managed endpoints that routinely process untrusted web content.
Enforce browser-update policies and investigate devices unable to receive the fixed release.
Check Google and Chromium guidance for any platform-specific instructions or revisions.
Validation and detection
Inventory installed Chrome versions and identify builds older than 151.0.7922.72.
Confirm managed devices completed the update and restarted Chrome where required.
Verify browser policies cannot pin systems to a vulnerable release.
Review security telemetry for renderer compromises or browser sandbox anomalies.
Recheck vendor advisories for revised affected-version or exploitation information.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · low confidence lookup
CWE-20: 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.
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.
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.
1CVSS vectors
3Timeline events
1ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-20 · source CWE mapping
Improper Input Validation
Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.