Quick answers
- Is CVE-2026-11297 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-11297 being exploited in the wild.
- How severe is CVE-2026-11297?
- Informational severity, with a CVSS score of 2, published 5 June 2026.
- Which products and versions are affected?
- Google Chrome for Android prior to 149.0.7827.53.
- Is there a fix for CVE-2026-11297?
- A patch was published on 2026-06-02: Chrome 149 promoted to stable channel Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-11297 attacked?
- It is attacked with local access, in a network appliance.
- Am I affected by CVE-2026-11297?
- Check whether you run 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 improper input validation vulnerability (CWE-20) exists in the Reader Mode component of Google Chrome for Android. The flaw stems from insufficient validation of untrusted input when processing files within Reader Mode. A local attacker can exploit this by providing a specially crafted malicious file to bypass navigation restrictions. This could potentially allow the attacker to circumvent security boundaries that normally restrict page transitions or origin-based access. The vulnerability is addressed in version 149.0.7827.53.
Affected products
- Google Chrome for Android prior to 149.0.7827.53
Timeline
- 2026-06-02: patched: Chrome 149 promoted to stable channel
- 2026-06-05: disclosed: NVD publication date