Is CVE-2026-8535 exploited in the wild?

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

How severe is CVE-2026-8535?

Medium severity, with a CVSS score of 5.3, published 14 May 2026.

Which products and versions are affected?

Google Chrome prior to 148.0.7778.168, Prior to 148.0.7778.168; Google ChromeOS prior to 148.0.7778.168, Prior to 148.0.7778.168.

Is there a fix for CVE-2026-8535?

A patch was published on 2026-05-12: Stable channel update released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-8535 attacked?

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

Am I affected by CVE-2026-8535?

Check whether you run Google Chrome, Google Chrome Os, Google ChromeOS or one of the others listed 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-8535: Google Chrome out of bounds read in Media component

CVE-2026-8535 · Severity: medium · CVSS 5.3 · Published 2026-05-14

A security vulnerability in Google Chrome's media handling component could allow an attacker to access sensitive information from the browser's memory. This issue affects users on Linux and ChromeOS who view a specially crafted JPEG image. An exploit could lead to the exposure of private data, though it typically requires the attacker to have already partially compromised a part of the browser's internal processing.

Technologies: Google Chrome, Google Chrome Os, Google ChromeOS, Linux Kernel. Vendors: Google, Linux.

Quick answers

Is CVE-2026-8535 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-8535 being exploited in the wild.
How severe is CVE-2026-8535?: Medium severity, with a CVSS score of 5.3, published 14 May 2026.
Which products and versions are affected?: Google Chrome prior to 148.0.7778.168, Prior to 148.0.7778.168; Google ChromeOS prior to 148.0.7778.168, Prior to 148.0.7778.168.
Is there a fix for CVE-2026-8535?: A patch was published on 2026-05-12: Stable channel update released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-8535 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-8535?: Check whether you run Google Chrome, Google Chrome Os, Google ChromeOS or one of the others listed 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

An out-of-bounds read vulnerability (CWE-125) exists in the Media component of Google Chrome and ChromeOS. The flaw is triggered when processing a specially crafted JPEG file. While the vulnerability is reachable remotely, the advisory notes it specifically allows an attacker who has already compromised the renderer process to read sensitive information from process memory. This could be used to bypass security mitigations like ASLR or to leak user data handled within that process. The issue is resolved in version 148.0.7778.168 and later.

Affected products

Google Chrome prior to 148.0.7778.168
Google ChromeOS prior to 148.0.7778.168

Timeline

2026-03-23: disclosed: Reported to Chrome by Google internal researchers
2026-05-12: patched: Stable channel update released
2026-05-14: advisory: NVD publication date

References

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