Loading story…
Google released Chrome 151 to patch five high-severity vulnerabilities affecting core browser components including V8, Blink, Chrome Extensions, HTML processing, and TabStrip. The flaws are described as use-after-free issues that could be triggered through malicious web content or extension interactions, potentially causing browser crashes, information disclosure, or arbitrary code execution on affected systems.
The affected versions are Chrome releases earlier than 151.0.7922.137/.138 on Windows and macOS and earlier than 151.0.7922.137 on Linux. Google said the stable-channel rollout will occur over days and weeks and is withholding detailed technical information and proof-of-concept material until most users have updated, while national and industry security notices urged users and enterprise administrators to deploy the update promptly.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
6 events from the most recent confirmed update back to the earliest known activity.
Huynh Dinh Vu, also known as WinD39, reported CVE-2026-19560, a high-severity use-after-free vulnerability in Chrome's Blink rendering engine.
Google internally discovered CVE-2026-19559, a high-severity use-after-free vulnerability in Chrome's HTML processing layer.
A researcher using the handle @bean5oup reported CVE-2026-19558, a high-severity use-after-free vulnerability in Chrome Extensions.
Jihyeon Jeong of Compsec Lab at Seoul National University reported CVE-2026-19556, a high-severity use-after-free vulnerability in Chrome's V8 JavaScript engine, to Google.
Google internally discovered CVE-2026-19557, a high-severity use-after-free vulnerability in Chrome's TabStrip interface.
Google released Chrome 151 to the Stable channel, patching five high-severity use-after-free vulnerabilities affecting V8, Blink, Chrome Extensions, HTML processing, and TabStrip. The patched versions are 151.0.7922.137/.138 for Windows and macOS and 151.0.7922.137 for Linux, and Google restricted technical details and PoCs until most users update.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
5 references tracked. Mallory keeps watching after this page renders.
cybersecuritynews.com
Open sourceacn.gov.it
Open sourcegmcsirt.gm
Open sourcechromereleases.googleblog.com
Open sourcecirt.gy
Open sourceMap 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.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Google released Chrome 151 Stable for desktop to address a large set of security issues, including **seven critical vulnerabilities** and hundreds of additional flaws across core browser components. The update brings Chrome to `151.0.7922.71/.72` on Windows and macOS and `151.0.7922.71` on Linux, and fixes weaknesses in areas including Compositing, Dawn, Views, Skia, Updater, ANGLE, Ozone, V8, WebGL, Media, and Chrome for iOS. Reported impacts include arbitrary code execution, sandbox escape, privilege escalation, information disclosure, data corruption, and bypass of security restrictions. The critical issues, tracked as `CVE-2026-17650` through `CVE-2026-17656`, include use-after-free bugs, a race condition, and insufficient validation of untrusted input. Google said the release contains **370 security fixes** overall, while public advisories highlighted 78 newly identified vulnerabilities, including 71 rated high severity, and noted that detailed bug information will remain temporarily restricted until most users are patched or dependent third-party fixes are available. Enterprises and users are being urged to update supported Chrome installations promptly as the rollout proceeds over days and weeks.
Aug 11, 2026
Google released Chrome 151 to fix **41 newly identified vulnerabilities** affecting the browser on Windows, macOS, and Linux, including **six critical flaws** and **35 high-severity issues**. The patched bugs include five **use-after-free** vulnerabilities in **WebGL, Aura, Skia, and Views**, as well as an **out-of-bounds write** in the **ANGLE** graphics engine. Google said the update is rolling out as versions **`151.0.7922.108/.109`** for Windows and macOS and **`151.0.7922.108`** for Linux. The vulnerabilities could lead to **arbitrary code execution, information disclosure, privilege escalation, security restriction bypass, denial of service, crashes, and data corruption**, with more than two dozen tied to memory-safety weaknesses. Google did not report active exploitation in the wild, but users and organizations were urged to update systems running versions prior to the patched releases as soon as possible.
Aug 7, 2026
Google released a Chrome 150 Stable security update that patches **27 vulnerabilities**, including two critical use-after-free flaws that could lead to remote code execution if a user visits a malicious webpage. The most severe issues are **`CVE-2026-15112`** in Chrome’s Ozone platform abstraction layer and **`CVE-2026-15129`** in the Views UI framework. Patched versions are **`150.0.7871.114/.115`** for Windows and macOS and **`150.0.7871.114`** for Linux. The update also fixes 13 use-after-free bugs overall, along with integer overflow, out-of-bounds access, uninitialized use, and insufficient validation issues affecting components including **V8, ANGLE, Autofill, WebRTC, Codecs, Extensions, Forms, Payments,** and **Navigation**. Google said most flaws were found internally, with only three reported externally for a combined **$3,000** in bug bounty rewards, and said there is no indication of active exploitation, though the volume of memory-safety defects raises the risk of weaponization.
Jul 10, 2026