Is CVE-2026-17656 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-17656 being exploited in the wild.

How severe is CVE-2026-17656?

Informational severity, with a CVSS score of 10, published 30 July 2026.

Which products and versions are affected?

Google Chrome prior to 151.0.7922.72.

Is there a fix for CVE-2026-17656?

A patch was published on 2026-07-29: Fixed in Stable Channel Update 151.0.7922.72 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-17656 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-17656?

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.

CVE-2026-17656: Google Chrome use after free in Ozone

CVE-2026-17656 · Severity: info · CVSS 10 · Published 2026-07-30

A critical security vulnerability has been identified in Google Chrome's Ozone component, which handles low-level graphics and input. An attacker could exploit this flaw by tricking a user into visiting a specially crafted website, potentially allowing the attacker to bypass the browser's security sandbox. If successful, this could lead to unauthorized access to the underlying operating system and the user's private data.

Technologies: Google Chrome. Vendors: Google.

Quick answers

Is CVE-2026-17656 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-17656 being exploited in the wild.
How severe is CVE-2026-17656?: Informational severity, with a CVSS score of 10, published 30 July 2026.
Which products and versions are affected?: Google Chrome prior to 151.0.7922.72.
Is there a fix for CVE-2026-17656?: A patch was published on 2026-07-29: Fixed in Stable Channel Update 151.0.7922.72 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-17656 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-17656?: 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 use-after-free vulnerability exists in the Ozone abstraction layer of Google Chrome. The flaw is triggered when the browser incorrectly manages memory during the processing of crafted HTML content. A remote, unauthenticated attacker can exploit this by inducing a user to visit a malicious webpage, leading to memory corruption. This corruption can be leveraged to achieve a sandbox escape, allowing for arbitrary code execution outside of the restricted browser environment. Google has addressed this issue in version 151.0.7922.72 for Windows and Mac, and 151.0.7922.71 for Linux.

Affected products

Google Chrome prior to 151.0.7922.72

Timeline

2026-06-14: disclosed: Reported to Chromium by Google researchers
2026-07-29: patched: Fixed in Stable Channel Update 151.0.7922.72
2026-07-30: advisory: NVD publication date

References

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