Tia N.List

Reported by 4 outlets

Chrome 152 Patches Over 300 Vulnerabilities

hot0.0
Why this score
Breadth
2.00 / 2.0 · 4 sources
Authority
1.80 / 2.0 · best outlet weight
Severity
3.70 / 5.0 · CVSS + content signals
Velocity
0.00 / 2.0 · updates in 48h
Pickup speed
0.58 / 0.6 · time to second source
Recency
× 0.00 temporal multiplier
Community
+ 0.00 / 1.5 · reddit signal
Score
0.0 / 10 = base × recency + community
securityweek.comgbhackers.comcyberpress.orgmalware.news CVE-2026-19556CVE-2026-19557CVE-2026-19558CVE-2026-19559CVE-2026-19560CVE-2026-76017CVE-2026-76018CVE-2026-76019CVE-2026-76020CVE-2026-76021CVE-2026-76022CVE-2026-76023CVE-2026-79282 first seen 62d ago

Timeline

  1. original reporting

    Chrome 152 Patches Over 300 Vulnerabilities

    securityweek.com · 48d ago · August 26th, 2026

  2. update from cyberpress.org

    Google Chrome Patches Multiple Browser Flaws That Could Enable Remote Attacks

    cyberpress.org · 62d ago · August 12th, 2026

    Google has released a new Chrome Stable Channel update for desktop platforms, fixing five high-severity security vulnerabilities that affect core browser components. The flaws include multiple use-after-free memory-safety issues that, if successfully exploited, could potentially enable remote attacks through malicious web content. The update moves Chrome to version 151.0.7922.137/.138 on Windows and macOS, while Linux users receive version 151.0.7922.137. Google Chrome Patches Multiple Browser Flaws All five security issues addressed in the release carry a High severity rating. The vulnerabilities span Chrome’s JavaScript engine, interface components, extension framework, HTML processing, and Blink rendering engine. CVE Component Vulnerability type Reporter CVE-2026-19556 V8 Use-after-free Jihyeon Jeong, Compsec Lab / Seoul National University CVE-2026-19557 TabStrip Use-after-free Google CVE-2026-19558 Extensions Use-after-free @bean5oup CVE-2026-19559 HTML Use-after-free Google CVE-2026-19560 Blink Use-after-free WinD39 / Huynh Dinh Vu CVE-2026-19556, affecting the V8 JavaScript and WebAssembly engine, was reported on July 15, 2026, and earned a $500 bug bounty. V8 flaws are particularly significant because web applications routinely process attacker-controlled JavaScript. A threat actor may attempt to deliver exploit code via a weaponized website, a phishing link, a compromised advertisement, or content hosted on a legitimate but breached domain. Use-after-free vulnerabili

  3. update from gbhackers.com

    Google Chrome 151 Update Fixes 5 High-Severity Use-After-Free Vulnerabilities

    gbhackers.com · 62d ago · August 12th, 2026

    Google Chrome 151 Update The rollout of this Stable channel update began on Tuesday, August 11, 2026. Google […] The post Google Chrome 151 Update Fixes 5 High-Severity Use-After-Free Vulnerabilities appeared first on GBHackers Security | #1 Globally Trusted Cyber Security News Platform .

  4. update from malware.news

    Google security advisory (AV26-806)

    malware.news · 62d ago · August 12th, 2026

    Serial number: AV26-806 Date: August 12, 2026 As of August 11, 2026, Google is affected by a vulnerability in the following product: Chrome versions prior to 151.0.7922.138 The Cyber Centre encourages users and administrators to review the provided web link and apply any necessary updates as they become available.

  5. update from gbhackers.com

    Google Chrome 151 Update Fixes 7 Security Flaws Enabling Remote Code Execution and Sandbox Escape

    gbhackers.com · 53d ago · August 21st, 2026

    Among these vulnerabilities is a critical use-after-free flaw, along with several high-severity issues affecting various components of the browser, including V8, DOM, Workers, networking, and Linux toolkit theming.

  6. update from cyberpress.org

    Google Chrome 151 Patches Critical Use-After-Free Bug and Six High-Severity Flaws

    cyberpress.org · 53d ago · August 21st, 2026

    Announced on August 20, 2026, the release addresses seven security vulnerabilities, one of which is rated Critical severity. Use-after-free bugs occur when a program continues referencing a memory location after it has been freed, which attackers can often exploit to execute arbitrary code or crash the browser. Google credited its own internal team for reporting the issue on June 11, 2026. Google Chrome 151 Patches Critical Use-After-Free Flaws Because Chromoting handles remote-access sessions, a successful exploit could potentially allow an attacker to hijack a remote connection or execute code on the host system, making this the standout fix in this cycle. The remaining six fixes are all rated High severity and span a wide range of Chrome subsystems, from the JavaScript engine to platform-specific theming code: CVE ID Severity Vulnerability Type Affected Component CVE-2026-76017 Critical Use after free Chromoting CVE-2026-76018 High Privilege elevation Import CVE-2026-76019 High Incorrect authorization Workers CVE-2026-76020 High Race condition V8 CVE-2026-76021 High Use after free DOM CVE-2026-76022 High Buffer overflow Network CVE-2026-76023 High Improper resource control Linux Tool

  7. update from gbhackers.com

    Google Chrome 152 Patches 327 Security Flaws, Including 10 Critical Vulnerabilities

    gbhackers.com · 48d ago · August 26th, 2026

    This stable-channel update is being rolled out as version 152.0.7977.64 for Linux and 152.0.7977.64/.65 for Windows and macOS.

  8. update from cyberpress.org

    Google Chrome 152 Patches 327 Security Flaws, Including 10 Critical Bugs

    cyberpress.org · 48d ago · August 26th, 2026

    The update is significant because it resolves a broad set of memory-safety, authorization, input validation, and information disclosure issues across Chrome’s graphics stack, browser interface, JavaScript engine, networking components, Safe Browsing, WebRTC, and Chromecast functionality. Most of Chrome 152’s Critical flaws involve use-after-free conditions , a memory-corruption category that occurs when software accesses memory after it has been freed. ANGLE is Chrome’s graphics translation layer, responsible for translating graphics API calls across platforms. Since it processes complex graphics content supplied by websites, it has long been considered a high-value browser attack surface. Google awarded the researcher, Goodluck, $25,000 for reporting the vulnerability. The release includes an improper

  9. update from malware.news

    Chrome before you browse again

    malware.news · 48d ago · August 26th, 2026

    The update includes 327 security fixes, ten of which address critical vulnerabilities. How to update Chrome If you don’t want to wait for the rollout to reach you, manually updating is easy. The easiest option is to allow Chrome to update automatically. But you can end up lagging behind on updates if you never close your browser or if something goes wrong, such as an extension preventing the update. To update manually, click the More menu (three dots), then go to Settings > About Chrome . If an update is available, Chrome will start downloading it automatically. Restart Chrome to complete the update, and you’ll be protected against these vulnerabilities. Chrome 152.0.7977.65 is up to date You can find an explanation of the version numbering system and step-by-step instructions in our guide: How to update Chrome on every operating system . Technical details We want to highlight two vulnerabilities out of the hundreds because we think they could attract attackers if they go unpatched for too long. Both can be triggered by simply visiting a mal

Covered in

digest 2026-08-27

Source on GitHub