Is CVE-2026-8572 exploited in the wild?

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

How severe is CVE-2026-8572?

Low severity, with a CVSS score of 3.1, published 14 May 2026.

Which products and versions are affected?

Google Chrome prior to 148.0.7778.168; Google Chrome for Android prior to 148.0.7778.168.

Is there a fix for CVE-2026-8572?

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

How is CVE-2026-8572 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-8572?

Check whether you run Google Android, Google Chrome or Google Chrome for Android 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-8572: Google Chrome insufficient policy enforcement in Network

CVE-2026-8572 · Severity: low · CVSS 3.1 · Published 2026-05-14

A security vulnerability in Google Chrome on Android could allow a remote attacker to access sensitive data from other websites. This occurs when an attacker uses a specially crafted webpage to bypass security boundaries that normally keep data from different sites separate. To exploit this, an attacker would first need to have already compromised a specific part of the browser's internal processing system.

Technologies: Google Android, Google Chrome, Google Chrome for Android. Vendors: Google.

Quick answers

Is CVE-2026-8572 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-8572 being exploited in the wild.
How severe is CVE-2026-8572?: Low severity, with a CVSS score of 3.1, published 14 May 2026.
Which products and versions are affected?: Google Chrome prior to 148.0.7778.168; Google Chrome for Android prior to 148.0.7778.168.
Is there a fix for CVE-2026-8572?: A patch was published on 2026-05-12: Stable channel update released for desktop and Android versions. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-8572 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-8572?: Check whether you run Google Android, Google Chrome or Google Chrome for Android 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 insufficient policy enforcement vulnerability exists in the Network component of Google Chrome for Android. The flaw allows a remote attacker who has already compromised the renderer process to bypass Same-Origin Policy (SOP) protections. By enticing a user to visit a crafted HTML page, the attacker can leak cross-origin data. This vulnerability is addressed in version 148.0.7778.168.

Affected products

Google Chrome prior to 148.0.7778.168

Timeline

2026-05-12: patched: Stable channel update released for desktop and Android versions.
2026-05-14: disclosed: CVE published to the NVD.

References

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