Skip to main content
VulnerabilityPublished Updated

CVE-2026-17658: Google Chrome · Use After Free

Affects Google ChromeSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High : upgrade to 151.0.7922.72 soon.

Data as of 27 Oct 2026, 05:11 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 35% 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:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Upgrade Google Chrome to 151.0.7922.72.

Affected software

ProductAffectedFixed in
GoogleChromeAffected
  • >=151.0.7922.72 <151.0.7922.72
Fixed in
  • 151.0.7922.72

AI-suggested

Users and administrators should update Google Chrome to version 151.0.7922.72 or later, where this vulnerability is patched. The vendor advisory confirms the availability of this fix. Applying this update eliminates the risk posed by this vulnerability.

Description

CVE-2026-17658 is a use-after-free vulnerability in the V8 JavaScript engine of Google Chrome versions prior to 151.0.7922.72. This flaw allows a remote attacker to execute arbitrary code within the browser's sandbox by delivering a crafted HTML page. The vulnerability has a high severity rating with a CVSS score of 8.8. No known exploits in the wild have been reported. Google has released a stable channel update to address this issue.

References

Community reviews

Loading reviews…