Chrome Desktop Update Fixes 28 Flaws Including Critical Memory Corruption Bugs
Google released a Stable Channel update for Chrome Desktop, upgrading Windows and Mac to 149.0.7827.114/.115 and Linux to 149.0.7827.114, to address 28 security vulnerabilities across components including Core, DigitalCredentials, Accessibility, GPU, WebMIDI, Network, DevTools, Extensions, Video, and Views. The release includes five critical flaws, notably multiple use-after-free bugs, a heap buffer overflow in GPU, and insufficient validation of untrusted input in Accessibility; Google said technical details will remain restricted until most users are patched or dependent third-party fixes are available.
Published CVE records tied to the release highlight several high-severity issues: CVE-2026-12013, a Chrome Media use-after-free on Windows that could be triggered through a crafted HTML page; CVE-2026-12014, a Cast use-after-free that could enable a sandbox escape from the local network segment via malicious network traffic; CVE-2026-12016, a DevTools flaw that could allow sandbox escape after renderer compromise; and CVE-2026-12018, a Mojo issue that could lead to OS-level privilege escalation on Windows through a malicious file. The Canadian Centre for Cyber Security urged users and administrators running versions prior to the patched builds to review Google’s advisory and apply updates as they become available.

Get ahead of threats like this
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
How this story unfolded
4 events from the most recent confirmed update back to the earliest known activity.
Canadian Centre for Cyber Security issues Chrome advisory
On June 12, 2026, the Canadian Centre for Cyber Security published advisory AV26-593 about Google's June 11 Chrome security update. It advised users and administrators to review Google's advisory and apply the necessary updates for affected desktop Chrome versions.
CVE entries are updated with CVSS details
On June 12, 2026, CVE records for several Chrome vulnerabilities were updated to add CVSS v3.1 vectors and related classification details. The updates affected entries including CVE-2026-12014, CVE-2026-12013, CVE-2026-12016, and CVE-2026-12018.
CVE records for multiple Chrome flaws are received
On June 11, 2026, CVE records were received for several Chrome vulnerabilities including CVE-2026-12013, CVE-2026-12016, and related issues referenced in the Chrome release. These records covered flaws such as a Media use-after-free, a DevTools sandbox escape, and other high-severity bugs affecting versions prior to 149.0.7827.115.
Google releases Chrome 149.0.7827.114/.115 with 28 security fixes
On June 11, 2026, Google announced a Stable Channel update for Chrome Desktop: version 149.0.7827.114/.115 for Windows and Mac and 149.0.7827.114 for Linux. The release addressed 28 security issues, including multiple critical and high-severity vulnerabilities across components such as Core, Accessibility, GPU, DevTools, and Media.
Related entities
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
Sources
6 references tracked. Mallory keeps watching after this page renders.
Google Chrome security advisory (AV26-593) - Canadian Centre for Cyber Security
cyber.gc.ca
Open sourceCVE-2026-12016 - Google Chrome DevTools Sandbox Escape
cvefeed.io
Open sourceChrome Releases: Stable Channel Update for Desktop
chromereleases.googleblog.com
Open sourceCVE-2026-12014 - Chrome Use-after-free Sandbox Escape
cvefeed.io
Open sourceCVE-2026-12013 - Google Chrome Use-After-Free
cvefeed.io
Open sourceCVE-2026-12018 - Google Chrome Mojo Privilege Escalation
cvefeed.io
Open sourceSee the full picture, correlated to your attack surface.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.


