Quick answers
- Is CVE-2026-11080 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-11080 being exploited in the wild.
- How severe is CVE-2026-11080?
- Informational severity, published 4 June 2026.
- Which products and versions are affected?
- Google WebView prior to 149.0.7827.53.
- Is there a fix for CVE-2026-11080?
- A patch was published on 2026-06-02: Stable channel update released for desktop and mobile components. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-11080 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-11080?
- Check whether you run Google WebView 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 WebView component of Google Chrome for Android prior to version 149.0.7827.53. The flaw is triggered when the application incorrectly manages memory during the processing of HTML content, leading to heap corruption. A remote, unauthenticated attacker can exploit this by inducing a user to load a malicious HTML page. Successful exploitation could lead to arbitrary code execution within the context of the sandboxed renderer process or a denial-of-service (browser crash). The issue is tracked as CWE-416 and has been addressed in the stable channel update.
Affected products
- Google Chrome WebView prior to 149.0.7827.53
Timeline
- 2026-06-02: patched: Stable channel update released for desktop and mobile components.
- 2026-06-04: disclosed: CVE-2026-11080 published.