Google has released Chrome version 153.0.8010.47, which patches 19 security vulnerabilities in the browser. According to NVD records, most of the flaws are rated high, and five of them are critical with a score of 9.6. Some of the vulnerabilities could allow an attacker to execute code outside the browser’s sandbox. The release has been rolled out to Chrome’s stable channel for Windows, macOS and Linux.
The five highest-scoring vulnerabilities
Five vulnerabilities with a CVSS score of 9.6 stand out this round. All of them are based on scenarios that lure the user into opening a crafted web page:
- CVE-2026-91728 — Integer overflow in the V8 JavaScript engine. Code can be executed inside the sandbox via a crafted HTML page.
- CVE-2026-91718 — Use-after-free in the Core component. It carries a risk of code execution outside the sandbox.
- CVE-2026-91716 — Use-after-free in the Auth component; accessing freed memory after use opens the door to code execution outside the sandbox.
- CVE-2026-91710 — Use-after-free in the WebAppInstalls component; this too can lead to code execution outside the sandbox.
- CVE-2026-91729 — Use-after-free in the DigitalCredentials component. Exploiting this one requires the attacker to use social engineering.
Other critical and high-severity vulnerabilities
Among the vulnerabilities on the list, CVE-2026-91721 is marked as critical on the Chromium side due to a use-after-free in the Internals component; its CVSS score is 8.8. Four more vulnerabilities share the same score: use-after-free in the PDF component (CVE-2026-91737), use-after-free in the DOM component (CVE-2026-91736), an out-of-bounds write in ServiceWorker (CVE-2026-91711) and a type confusion in ServiceWorker (CVE-2026-91709, CVE-2026-91715). The use-after-free in the Input component (CVE-2026-91722) and the type confusion in Compositing (CVE-2026-91731) are also in the 8.8 group.
In the medium-to-high band, meanwhile, we have improper authorization in WebUI (CVE-2026-91735), improper state validation in Skia (CVE-2026-91733), a second use-after-free entry in Input (CVE-2026-91724) and a race condition in the Extensions component on macOS (CVE-2026-91712), all with a score of 8.3. Improper reference resolution in the Extensions component on Mac (CVE-2026-91727) scored 8.1, while improper authorization in the Core component on Windows (CVE-2026-91734) scored 7.4; that last vulnerability lets a local attacker execute code outside the sandbox.
No information on active exploitation
Google has not shared any information indicating that these vulnerabilities are currently being actively exploited. None of the CVEs appear in CISA’s Known Exploited Vulnerabilities (KEV) catalog, so there is no known wave of attacks. Even so, the high scores and the fact that most of the flaws can cross the sandbox boundary are reason enough not to put off updating.
How to update
Chrome usually updates itself in the background, but the new version only takes effect once the browser is restarted. To check the version, type chrome://settings/help into the address bar. Chrome checks for updates on startup; once the download is complete, a “Relaunch” button appears on the same page. After that, simply closing and reopening the browser completely is enough. Chrome restores your session so any open tabs and windows come back, meaning there’s no risk of losing your work.
In corporate environments, Chrome updates are usually distributed through central management tools. Even so, verifying that the version number hasn’t fallen below 153.0.8010.47 is the easiest step toward closing off the most common entry point for browser-based attacks.
Source: CISA KEV · NVD

Share your experience
Bir sorunun, farklı bir çözümün veya eklemek istediğin bir notun var mı? Giriş yapmadan da yazabilirsin.