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 cve
About this tag
The chrome cve tag covers disclosed vulnerabilities in Google Chrome, with a focus on Windows users and administrators. Recent threads detail high-severity flaws such as use-after-free bugs in ServiceWorker, Read Anything, Payments, Bluetooth, and Views UI components, as well as input-validation issues in Extensions that can bypass site isolation. Many of these CVEs require a compromised renderer to achieve sandbox escape or code execution, making them critical for enterprise patch management. The tag emphasizes the importance of updating Chrome and Chromium-based browsers to mitigate these security risks, particularly for Windows systems.
Google documented CVE-2026-14022 on June 30, 2026, as a medium-severity Chrome Network vulnerability fixed before version 150.0.7871.47 that could let an attacker with a compromised renderer process leak cross-origin data through a crafted HTML page. The National Vulnerability Database entry...
Google Chrome CVE-2026-14078 is a WebRTC input-validation flaw fixed in Chrome 150.0.7871.47, published by Chrome on June 30, 2026, and later enriched by NVD and CISA as a remotely reachable privilege-escalation issue triggered through a crafted HTML page. The uncomfortable part is not that...
Google Chrome before version 150.0.7871.47 contained CVE-2026-14109, a Mojo policy-enforcement flaw disclosed on June 30, 2026, that could let an attacker escape the browser sandbox after first compromising a renderer process with a crafted HTML page. The awkward part is not that Chrome had...
Google Chrome CVE-2026-14110 was published by NVD on June 30, 2026, after Chrome reported that versions before 150.0.7871.47 could let a remote attacker spoof browser UI through a crafted HTML page because of an inappropriate DarkMode implementation. The bug is rated low by Chromium but scored...
Google Chrome CVE-2026-13957 was published by NVD on June 30, 2026, modified by CISA-ADP on July 1, and initially analyzed by NIST on July 2 as an Extensions security-UI flaw affecting Chrome versions before 150.0.7871.47. The short answer to the CPE question is: probably not, at least not for...
Google Chrome before version 150.0.7871.47 contains CVE-2026-13894, a medium-severity Chromium Network flaw disclosed on June 30, 2026, that lets an attacker in a privileged network position bypass navigation restrictions using a crafted HTML page. The bug is not the loudest item in Chrome 150’s...
Google Chrome before 149.0.7827.197 contained CVE-2026-13024, a high-severity Chromium navigation flaw disclosed on June 24, 2026, that could let an attacker who had already compromised Chrome’s renderer process bypass site isolation with a crafted HTML page. That narrow precondition is the...
Google disclosed CVE-2026-13026 on June 24, 2026, as a high-severity use-after-free flaw in Chrome’s Digital Credentials implementation on macOS, fixed in Chrome 149.0.7827.197 after a crafted HTML page could potentially trigger heap corruption with user interaction. The advisory is narrow, but...
Google disclosed CVE-2026-11694 on June 8, 2026, as a high-severity use-after-free flaw in Chrome’s ServiceWorker code before version 149.0.7827.103 that could let a remote attacker, after compromising the renderer process, execute code inside Chrome’s sandbox using a crafted HTML page. The...
Google disclosed CVE-2026-11692 on June 8, 2026, as a high-severity use-after-free flaw in Chrome’s Read Anything feature before version 149.0.7827.103, where a crafted HTML page could help an attacker who had already compromised the renderer process attempt a sandbox escape. That phrasing is...
Google Chrome CVE-2026-11664 is a high-severity use-after-free flaw in Chrome’s Payments component, disclosed June 8, 2026, affecting Chrome versions before 149.0.7827.103 and potentially exploitable by a remote attacker through a crafted HTML page. The bug is not the headline-grabbing zero-day...
Google Chrome’s CVE-2026-11658, published June 8, 2026 and last modified by NVD on June 10, describes an Extensions input-validation flaw in Chrome before 149.0.7827.103 that could let an attacker with a compromised renderer bypass site isolation using a crafted HTML page. The bug is not the...
Google fixed CVE-2026-11641 on June 8, 2026, in Chrome’s Stable Channel update for desktop, closing a critical Windows-only use-after-free flaw in the browser’s Bluetooth code before version 149.0.7827.103 that could let a remote attacker execute code through a crafted web page. The detail that...
Google Chrome on macOS before version 149.0.7827.103 contained CVE-2026-11637, a critical use-after-free flaw in the browser’s Views UI framework that could let a remote attacker execute arbitrary code through a crafted HTML page. The bug was published by Chrome on June 8, 2026, enriched by CISA...
Google disclosed CVE-2026-12017 on June 11, 2026, as a high-severity Chrome Extensions flaw fixed in Chrome 149.0.7827.114/.115 for desktop, where a compromised renderer could use a crafted HTML page to bypass site isolation. The dry wording makes it sound like just another browser bulletin, but...
Google Chrome on Windows before version 148.0.7778.96 contains CVE-2026-7911, a high-severity use-after-free flaw in Chromium’s Aura UI layer that could let a remote attacker who already compromised the renderer attempt a sandbox escape through a crafted HTML page. That phrasing is dry, but the...
Google and Microsoft patched CVE-2026-7349 this week after Chrome’s Cast component was found vulnerable to a high-severity use-after-free flaw that could let an attacker on the same local network segment execute code inside Chrome’s sandbox through malicious network traffic. The fixed Chrome...
Google’s latest Chromium security disclosure, CVE-2026-5860, is another reminder that browser bugs rarely stay “just browser bugs” for long. Microsoft’s Security Update Guide records the issue as a use-after-free in WebRTC affecting Google Chrome versions prior to 147.0.7727.55, and the record...