Advisories illustration
Google promoted Chrome 153 to the Stable channel for Windows, Mac and Linux on 8 September 2026, in a release signed by Srinivas Sista. The notes said the desktop build was 153.0.8010.36 on Linux and 153.0.8010.36 or .37 on Windows and Mac, rolling out over coming days and weeks. The update included 230 security fixes. Buried in a long list of memory-safety bugs is a sentence Google uses only when it believes attackers are already ahead of the patch: the company is aware that an exploit for CVE-2026-87491 exists in the wild. That CVE is described in the same notes as a medium-severity out-of-bounds write in V8, Chrome’s JavaScript and WebAssembly engine, reported by Jihyeon Jeong of the Compsec Lab at Seoul National University, listed as a research intern, on 6 August 2026. An out-of-bounds write in V8 is the sort of bug that, if successfully exploited, can let a crafted web page run code inside the browser sandbox. Google did not say who was using the exploit, how it was delivered, or which organisations were targeted. Those details remain unconfirmed in the public release. On 9 September 2026, the U.S. Cybersecurity and Infrastructure Security Agency added CVE-2026-87491 to its Known Exploited Vulnerabilities catalog, describing it as a Chromium V8 out-of-bounds write that can allow arbitrary code execution inside the sandbox via a crafted HTML page. CISA noted that the issue could affect other Chromium-based browsers, including Microsoft Edge and Opera, not only Google Chrome. CISA did not state in that alert whether the bug has been used in ransomware. Chrome 153’s security section also lists a large number of other high and critical fixes, many credited to Google’s own researchers, in components such as WebGL, ANGLE, Views and Payments. Those additional CVEs are not described in the notes as exploited in the wild. Readers should not treat the whole 230-fix list as equally urgent; Google singled out CVE-2026-87491. Because exploitation requires a victim to open a malicious page, the practical risk for households and small offices is drive-by content: compromised ads, fake news sites, or links in email and chat. Updating Chrome does not require a new licence or a specialist, but it does require a restart so the patched V8 engine is loaded. Other Chromium browsers typically lag Google’s Stable date by days; administrators should not assume Edge or Brave were patched on 8 September. What to do • In Chrome, open chrome://settings/help, allow the update to 153.0.8010.36 or later, and restart every window. • Update other Chromium browsers and any in-house apps that embed Chromium once their vendors publish a matching V8 fix. • Treat unexpected “your browser is out of date” pages as phishing. Use the browser’s own about or help page. • Small organisations should push the update through device management and confirm the version string, not merely that Chrome is installed. • If a machine visited untrusted sites before patching, review extensions, saved passwords and session cookies; Google has not published a public indicator list for this exploit. Primary source: Chrome Releases, “Stable Channel Update for Desktop”, 8 September 2026; CISA alert, 9 September 2026.

Sources

  1. Chrome Releases — Stable Channel Update for Desktop2026-09-24
  2. CISA — CISA Adds Four Known Exploited Vulnerabilities to Catalog2026-09-24

Cyber71 links the primary material behind each report so readers can check it directly. External pages are not under our control and may change.

All news

Need help with a security issue?

Describe the situation and we will open a private case for follow-up.

Get Security Help