You are using an out of date browser. It may not display this or other websites correctly. You should upgrade or use an alternative browser.
chrome on android
About this tag
This tag covers discussions about Chrome on Android vulnerabilities, focusing on CVE entries disclosed in June 2026. Topics include domain spoofing in Cronet, use-after-free in WebShare, WebAuthentication flaws, and GPU sandbox escape bugs, all fixed before Chrome version 149.0.7827.53. Threads analyze CPE confusion in NVD records, severity gaps between Chromium's Medium label and CISA's ADP scoring, and the implications for patch prioritization and exposure management. The content is relevant for IT administrators and security professionals managing mobile browser risks.
Google’s CVE-2026-11215, published June 4, 2026 and modified June 5, describes a medium-severity Chrome-on-Android flaw in Cronet before version 149.0.7827.53 that could let a remote attacker spoof a domain name using a crafted domain. The bug is not a memory-corruption panic button; it is a...
Google’s CVE-2026-11010 is a Chrome-on-Android WebShare use-after-free flaw disclosed on June 4, 2026, fixed before version 149.0.7827.53, and scored by CISA’s ADP process as a high-severity issue despite Chromium’s own “Medium” label. The oddity is not merely the mismatch between severity...
CVE-2026-11263 is a low-severity Chromium WebAuthentication flaw affecting Google Chrome on Android before version 149.0.7827.53, published by NVD on June 4, 2026, and mapped by NIST on June 8 to Chrome running on Android. The short answer to the CPE question is: probably not. The interesting...
Google Chrome’s CVE-2026-11119 was published by NVD on June 4, 2026, and describes a Chrome-on-Android GPU flaw fixed before version 149.0.7827.53 that could let an attacker escape the browser sandbox after first compromising the renderer with a crafted HTML page. The record is messy in exactly...