# CVE-2026-11291: Google Chrome for Android SOP bypass in Android Autofill

Source: https://junglewise.ai/threats/cve-2026-11291-google-chrome-for-android-sop-bypass-in-android-autofill  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-06-05. Updated: 2026-06-05  
License: CC BY 4.0 with a link back

CVE-2026-11291 · Severity: info · Published 2026-06-05

A security vulnerability exists in the Android Autofill component of Google Chrome for Android. This flaw could allow a malicious website to bypass the browser's Same Origin Policy, which is a fundamental security boundary that prevents websites from interacting with data from other sites. If exploited, an attacker could potentially access sensitive information or perform unauthorized actions on behalf of the user across different websites.

Technologies: [Google Chrome](https://junglewise.ai/threats/technologies/chrome). Vendors: [Google](https://junglewise.ai/threats/vendors/google).

## Quick answers

**Is CVE-2026-11291 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-11291 being exploited in the wild.

**How severe is CVE-2026-11291?** Informational severity, published 5 June 2026.

**Which products and versions are affected?** Google Chrome prior to 149.0.7827.53.

**Is there a fix for CVE-2026-11291?** A patch was published on 2026-06-02: Chrome 149.0.7827.53 released for stable channel Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-11291 attacked?** It is attacked over the network, in a network appliance.

**Am I affected by CVE-2026-11291?** 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

An inappropriate implementation vulnerability exists in the Android Autofill component of Google Chrome for Android prior to version 149.0.7827.53. The flaw allows a remote attacker to bypass the Same Origin Policy (SOP) by enticing a user to visit a specially crafted HTML page. By exploiting this weakness, an attacker can potentially access data or interact with web content from origins other than the one serving the malicious page. The vulnerability is categorized by Chromium as Low severity and has been addressed in the stable channel update.

## Affected products

- Google Chrome for Android prior to 149.0.7827.53

## Timeline

- 2026-06-02: patched: Chrome 149.0.7827.53 released for stable channel
- 2026-06-05: disclosed: CVE published in NVD dataset

## References

- [https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html](https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html)
- [https://issues.chromium.org/issues/502346855](https://issues.chromium.org/issues/502346855)

## Related threats

- [Google Chrome out of bounds read in Skia](https://junglewise.ai/threats/cve-2026-126922-out-of-bounds-read-in-skia-in-google-chrome-prior-to-157-0-8103)
- [Google Chrome use after free in Accessibility](https://junglewise.ai/threats/cve-2026-126921-use-after-free-in-accessibility-in-google-chrome-prior-to-157-0)
- [Google Chrome information leak in Skia](https://junglewise.ai/threats/cve-2026-126920-information-leak-in-skia-in-google-chrome-prior-to-157-0-8103-78)
- [Google Chrome use-after-free in BrowserTag](https://junglewise.ai/threats/cve-2026-126919-use-after-free-in-browsertag-in-google-chrome-prior-to-157-0)
- [Google Chrome use-after-free in Layout](https://junglewise.ai/threats/cve-2026-126918-use-after-free-in-layout-in-google-chrome-prior-to-157-0-8103-78)