chrome security

Google Chrome versions before 150.0.7871.46 are affected by CVE-2026-14414, a medium-severity Skia input-validation flaw. The confirmed security outcome is potential disclosure of sensitive information from process memory, but only after an attacker has already compromised Chrome’s renderer and...

Update and Verify Chrome on Windows Now On a Windows PC: Open Google Chrome. Enter chrome://settings/help in the address bar and press Enter. You can also select Menu ⋮ > Help > About Google Chrome. Let Chrome finish checking for an update. Confirm that the complete version shown is...

Google Chrome users on Windows should update to version 150.0.7871.46 or later to address CVE-2026-14429, a high-severity Skia input-validation vulnerability that may allow a remote attacker to escape Chrome’s sandbox through crafted HTML after first compromising a renderer process. That...

A Renderer Compromise Is the Required First Stage CVE-2026-14427 is not publicly described as a self-contained, one-step takeover of a clean Chrome installation. The Chrome-originated description says the attacker must already have compromised the renderer process before potentially using the...

Update Google Chrome to 150.0.7871.46 or later and relaunch it; CVE-2026-14425 affects earlier Chrome versions and may permit a sandbox escape through a crafted HTML page. Google rates the Chromium security severity as High, while a separate CISA-ADP contribution supplies a 9.6 Critical CVSS 3.1...

Google disclosed CVE-2026-14421 as a medium-severity uninitialized-use flaw in Chrome’s Dawn graphics component on ChromeOS. A remote attacker may be able to expose potentially sensitive process-memory data by persuading a user to open a crafted HTML page in a Chrome version earlier than...

Google Chrome versions earlier than 150.0.7871.46 are affected by CVE-2026-14420, a Critical out-of-bounds read and write in Dawn that could allow a remote attacker using a crafted HTML page to potentially escape the browser sandbox. The affected product established by the public record is...

CVE-2026-14416 is an out-of-bounds read in Chrome’s Dawn graphics component that affects versions before 150.0.7871.46 and could let a remote attacker use a crafted HTML page to cross the browser sandbox under favorable exploit conditions, even though Chromium labels the flaw Low severity. The...

Chrome 150.0.7871.46 is outside the documented affected range for CVE-2026-14417, a Critical use-after-free vulnerability in Dawn that could allow a remote attacker to potentially perform a sandbox escape via a crafted HTML page. The National Vulnerability Database record identifies applicable...

CVE-2026-14415: Update Chrome Past 150.0.7871.46—and Verify the Full Version After Relaunch Google fixed CVE-2026-14415 in Google Chrome 150.0.7871.46. Chrome installations below that complete four-part version are within the affected range identified by the National Vulnerability Database...

Google fixed CVE-2026-14413 in Chrome 150.0.7871.46 on June 30, 2026, closing a high-severity ANGLE memory-initialization flaw that could let an attacker who had already compromised a renderer process use crafted HTML to attempt an escape from Chromium’s browser sandbox. The prerequisite...

Google disclosed CVE-2026-14412 on July 1, 2026, a high-severity input-validation flaw in Chrome’s ANGLE graphics layer that could let an attacker who had already compromised a renderer process escape the browser sandbox through a crafted HTML page on versions earlier than 150.0.7871.46. The...

Google’s CVE-2026-14401 is a high-severity ANGLE input-validation flaw affecting Chrome on Android before version 150.0.7871.46. According to the Chrome-originated CVE description, a remote attacker who has already compromised the browser’s renderer can use a crafted HTML page to potentially...

Google Chrome versions earlier than 150.0.7871.46 are within the documented affected range for CVE-2026-14400, a high-severity out-of-bounds write in ANGLE that could potentially help an attacker escape Chrome’s sandbox after the renderer process had already been compromised. The prerequisite...

Google Chrome on macOS before version 150.0.7871.47 is affected by CVE-2026-13778, a use-after-free vulnerability in WebUSB that can allow a local attacker using a malicious peripheral to execute arbitrary code. The published record does not establish that Chrome on Windows or Linux, Microsoft...

Google disclosed CVE-2026-13966 on June 30, 2026, as a medium-severity Chrome History flaw fixed before version 150.0.7871.47, allowing a remote attacker to spoof browser interface cues through a crafted HTML page if the user interacted with it. The National Vulnerability Database later added...

Google Chrome’s June 30, 2026 desktop stable update fixed CVE-2026-13971, a medium-severity Skia memory-initialization flaw affecting Chrome before 150.0.7871.47 that could let an attacker with a compromised renderer read potentially sensitive process memory through a crafted HTML page. The bug...

Google Chrome before version 150.0.7871.47 contained CVE-2026-13982, a medium-severity flaw in the browser’s Passwords interface that could let an attacker spoof security UI after first compromising the renderer process with a crafted HTML page. The vulnerability was published by Chrome on June...

Google Chrome before version 150.0.7871.47 contains CVE-2026-13984, a medium-severity TabStrip flaw disclosed on June 30, 2026, that can let a remote attacker spoof security-related browser UI through a crafted HTML page. The bug is not a code-execution monster, and that is exactly why it is...

Google fixed CVE-2026-13990 in Chrome 150.0.7871.47 for Windows on June 30, 2026, closing a medium-severity DataTransfer input-validation flaw that could let an attacker, after compromising Chrome’s renderer process, spoof browser UI through a crafted HTML page. The entry is now live in the...