CHROME-2026-06-11

The Stable channel has been updated to 149.0.7827.114/.115 for Windows and Mac and 149.0.7827.114 for Linux, which will roll out over the coming days/weeks. A full list of changes in this build is available in the LogSecurity Fixes and RewardsNote: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed.This update includes 28 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information. Critical CVE-2026-12007: Use after free  Core. Reported by Google on 2026-05-26 Critical CVE-2026-12008: Use after free  DigitalCredentials. Reported by Google on 2026-05-27 Critical CVE-2026-12009: Insufficient validation of untrusted input  Accessibility. Reported by Google on 2026-05-28 Critical CVE-2026-12010: Heap buffer overflow  GPU. Reported by Google on 2026-05-28 Critical CVE-2026-12011: Use after free  WebMIDI. Reported by Google on 2026-05-30 High CVE-2026-12012: Use after free  Network. Reported by Google on 2026-04-03 High CVE-2026-12013: Use after free  Media. Reported by Henock Habte, Independent Security Researcher on 2026-05-18 High CVE-2026-12014: Use after free  Cast. Reported by Google on 2026-05-19 High CVE-2026-12015: Use after free  Autofill. Reported by Google on 2026-05-21 High CVE-2026-12016: Insufficient validation of untrusted input  DevTools. Reported by Google on 2026-05-25 High CVE-2026-12017: Insufficient validation of untrusted input  Extensions. Reported by Google on 2026-05-26 High CVE-2026-12018: Inappropriate implementation  Mojo. Reported by Google on 2026-05-26 High CVE-2026-12019: Out of bounds write  Codecs. Reported by Google on 2026-05-26 High CVE-2026-12020: Use after free  Autofill. Reported by Google on 2026-05-27 High CVE-2026-12022: Race  Safe Browsing. Reported by...