Loading story…
Google has released Chrome 151 to the stable channel, delivering a mix of user-facing, enterprise, and developer changes in the Chromium-based browser. The update adds new Gemini AI integrations, expands Safe Browsing protections, and improves PDF handling, while Google continues to distinguish Chrome from upstream Chromium through bundled components such as Google API integration, DRM support, and other Chrome-specific services. The release also keeps the Extended Stable channel available and indicates that Chrome 152 is planned as the next major version.
Chrome 151 also advances Google's transition away from legacy extensions by further restricting Manifest V2 add-ons, though enterprises retain a temporary policy option to allow older MV2 extensions during migration. On the platform side, the browser drops support for macOS 12 and now targets macOS 13+, while additional legacy browser features and APIs are being removed or deprecated, including older XML/XSLT-related functionality. The release further introduces web-platform updates for developers, including new HTML and PerformanceObserver capabilities, alongside broader changes affecting Windows, Linux, and macOS deployments.
See real exploitation activity before you spend the cycle.
1 event from the most recent confirmed update back to the earliest known activity.
Google released Chrome 151 as a new stable version of the Chrome browser based on Chromium. The release includes user-facing changes such as Gemini-related AI integrations, Safe Browsing enhancements, PDF improvements, enterprise controls for legacy Manifest V2 extensions, and platform/deprecation updates including ending support for macOS 12.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See real exploitation activity behind this advisory so you can triage it against everything else in the queue.
9 references tracked. Mallory keeps watching after this page renders.
securityweek.com
Open sourceopennet.ru
Open sourceopennet.me
Open sourcedeveloper.chrome.com
Open sourcedeveloper.chrome.com
Open sourcedeveloper.mozilla.org
Open sourcechromeenterprise.google
Open sourceblog.google
Open sourcechromium.googlesource.com
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** 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.
Aug 16, 2026
Google released Chrome 152.0.7977.75/.76 for Windows and macOS and 152.0.7977.75 for Linux, patching 26 vulnerabilities. The fixes include critical use-after-free flaws in Shared Tab Groups (`CVE-2026-84353`) and WebGL (`CVE-2026-84352`), which could allow malicious web content to crash the browser, disclose information, or potentially execute code in the browser process. The release also addresses nine high-severity issues and additional flaws affecting FileSystem, Skia, Omnibox, V8, GPU, WebRTC, Downloads, and TabStrip, including risks of code execution and security-control bypass. Google has not reported active exploitation; organizations should verify managed endpoints update to Chrome 152.0.7977.75 or later as the Stable-channel rollout progresses.
Sep 5, 2026
Google released Chrome 153 for Windows, macOS, Linux, Android, and iOS, fixing 230 reported security vulnerabilities, including **CVE-2026-87491**, an out-of-bounds write in the V8 JavaScript and WebAssembly engine that is reportedly being exploited in the wild. The release includes five critical and 43 high-severity fixes across WebGL, Cast, ANGLE, PDFium, V8, and WebView; organizations should prioritize updating managed browsers to `153.0.8010.36` or later. Google has formally reduced Chrome's stable release cycle from four weeks to two weeks, aiming to shorten the N-day window between public disclosure of a flaw and deployment of a patch. The company cited a growing volume of reports and automated AI-assisted security work, alongside faster-moving AI-enabled threats, as drivers for the accelerated cadence; the schedule will also speed delivery and iteration of Chrome features, including AI capabilities.
Sep 10, 2026