CVE-2026-17754: Blink · Inappropriate Implementation
Affects chromeSource GCVE Database
Not known to be exploited · CVSS 6.5 Medium : upgrade to 151.0.7922.72 when convenient.
Data as of 29 Oct 2026, 07:15 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 151.0.7922.72
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 30 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade google/chrome to 151.0.7922.72.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Googlegoogle/chromepkg:deb/google/chromeOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until then, exercising caution with untrusted web content and limiting user interaction with suspicious pages may reduce risk.
Description
A vulnerability in the Blink rendering engine of Google Chrome prior to version 151.0.7922.72 allows a remote attacker to bypass the same origin policy via a crafted HTML page. This issue is classified with medium severity and affects the integrity of web content isolation. The vulnerability does not impact confidentiality or availability directly. No known exploits are reported in the wild.