Skip to main content
VulnerabilityPublished Updated

CVE-2026-76047: Google Chrome · Type Confusion

Affects Google ChromeSource CVE Database V5

0
Compare

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

Data as of 15 Nov 2026, 20:25 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 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 151.0.7922.169
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 18 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 15 Nov 2026.

What to do

Upgrade Google Chrome to 151.0.7922.169.

Affected software

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

AI-suggested

An official fix is available from Google in the stable channel update for Chrome version 151.0.7922.169. Users and administrators should update affected Chrome installations to version 151.0.7922.169 or later to mitigate this vulnerability.

Description

CVE-2026-76047 is a high-severity type confusion vulnerability in the V8 JavaScript engine used by Google Chrome. It affects versions prior to 151.0.7922.169 and allows a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. The vulnerability has a CVSS score of 8.8, indicating a significant risk if exploited. Google has published a stable channel update addressing this issue.

References

Community reviews

Loading reviews…