Is CVE-2026-11028 exploited in the wild?

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

How severe is CVE-2026-11028?

Informational severity, published 4 June 2026.

Which products and versions are affected?

Google Chrome prior to 149.0.7827.53; Google ChromeOS prior to 149.0.7827.53.

Is there a fix for CVE-2026-11028?

A patch was published on 2026-06-02: Chrome 149.0.7827.53 released to stable channel Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-11028 attacked?

It is attacked over the network, in an operating system.

Am I affected by CVE-2026-11028?

Check whether you run Google Chrome or Google ChromeOS 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-11028: Google Chrome use after free in Media component

CVE-2026-11028 · Severity: info · Published 2026-06-04

A security vulnerability exists in the media processing component of Google Chrome for Linux and ChromeOS. This flaw could allow a remote attacker who has already partially compromised the browser's rendering process to execute malicious code. While the attack is limited by the browser's security sandbox, it represents a significant step in a multi-stage attack that could lead to unauthorized access to user data or system resources.

Technologies: Google Chrome, Google ChromeOS. Vendors: Google.

Quick answers

Is CVE-2026-11028 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-11028 being exploited in the wild.
How severe is CVE-2026-11028?: Informational severity, published 4 June 2026.
Which products and versions are affected?: Google Chrome prior to 149.0.7827.53; Google ChromeOS prior to 149.0.7827.53.
Is there a fix for CVE-2026-11028?: A patch was published on 2026-06-02: Chrome 149.0.7827.53 released to stable channel Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-11028 attacked?: It is attacked over the network, in an operating system.
Am I affected by CVE-2026-11028?: Check whether you run Google Chrome or Google ChromeOS 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 (UAF) vulnerability exists in the Media component of Google Chrome for Linux and ChromeOS. The flaw is triggered when the browser incorrectly manages memory during the processing of media content. An attacker can exploit this by enticing a user to visit a specially crafted HTML page. A successful exploit requires the attacker to have already compromised the renderer process; from there, they can leverage this UAF to execute arbitrary code within the confines of the browser's sandbox. The issue is addressed in version 149.0.7827.53.

Affected products

Google Chrome prior to 149.0.7827.53
Google ChromeOS prior to 149.0.7827.53

Timeline

2026-06-02: patched: Chrome 149.0.7827.53 released to stable channel
2026-06-04: disclosed: CVE published to NVD

References

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