CVE-2026-15776: Google Chrome type confusion in V8

CVE-2026-15776 · Severity: high · CVSS 8.8 · Published 2026-07-14

A security vulnerability has been identified in Google Chrome's V8 engine, which is responsible for processing JavaScript. An attacker could exploit this flaw by tricking a user into visiting a specially crafted website, potentially allowing the attacker to execute unauthorized code on the user's computer. While the exploit is limited to the browser's security sandbox, it represents a significant risk to data privacy and system integrity.

Technologies: Google Chrome. Vendors: Google.

Quick answers

Is CVE-2026-15776 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-15776 being exploited in the wild.
How severe is CVE-2026-15776?
High severity, with a CVSS score of 8.8, published 14 July 2026.
Which products and versions are affected?
Google Chrome Prior to 150.0.7871.125.
Is there a fix for CVE-2026-15776?
A patch was published on 2026-07-14: Stable channel update released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-15776 attacked?
It is attacked over the network, in a web application.
Am I affected by CVE-2026-15776?
Check whether you run Google Chrome at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A type confusion vulnerability (CWE-843) exists in the V8 JavaScript engine within Google Chrome. The flaw stems from an inappropriate implementation that allows a remote, unauthenticated attacker to achieve arbitrary code execution within the browser's sandbox. Exploitation requires a user to navigate to a malicious or compromised web page (User Interaction). The vulnerability was addressed in Chrome version 150.0.7871.125 for Windows and Mac, and 150.0.7871.124 for Linux.

Affected products

  • Google Chrome Prior to 150.0.7871.125

Timeline

  • 2026-07-08: disclosed: Reported to Chromium by Salvatore Gulizia
  • 2026-07-14: patched: Stable channel update released
  • 2026-07-14: advisory: NVD publication date

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.