Google has moved Chrome 156 to the stable channel. This isn’t just a feature release: the update fixes 353 security vulnerabilities, six of which are in the critical class, the highest level in Google’s own rating. The version number is 156.0.8078.47/.48 on Windows and macOS, and 156.0.8078.47 on Linux.
Google’s announcement does not state that any of the vulnerabilities have been exploited in real attacks. However, a patch list of this size makes delaying the update risky. The browser remains an attack surface as soon as a malicious page is opened.
Which critical vulnerabilities are they?
Five of the six critical vulnerabilities are memory corruption, and one is a use-after-free bug. The list is as follows: CVE-2026-113341 (Skia), CVE-2026-113279 (Accessibility), CVE-2026-113072 (CSS), CVE-2026-113280 (Paint), CVE-2026-113303 (WebRTC), and CVE-2026-113271 (Accessibility, use-after-free). What these bugs have in common is that memory can be corrupted through a crafted HTML page.
According to NVD records, 14 of the vulnerabilities fixed in the release are rated at CVSS 9.6. These vulnerabilities are defined as allowing code to run outside the sandbox. For the remaining 114 vulnerabilities, the impact stays inside the sandbox; in other words, the attacker would also need to bypass the browser’s security layer. According to Chromium’s own classification, the distribution is 6 critical, 61 high, 197 medium, and 89 low-severity vulnerabilities.
The list is dominated by memory bugs
Most of the vulnerabilities fixed in Chrome 156 are related to memory safety. Among the fixes are 163 memory corruption bugs, 125 use-after-free bugs, and 17 out-of-bounds read bugs. Of the rest, 36 are improper input validation bugs. This picture shows that memory safety debt is still the biggest item in the C++-based browser engine.
The practical consequence for users is this: most of these vulnerabilities can be triggered remotely through a malicious ad or a compromised site. The user does not need to download a file or click a link.
How to update
In Chrome, type chrome://settings/help in the address bar. The page checks the version; if you do not see 156.0.8078.47 or higher, start the update and restart the browser. If you do not restart after the update is downloaded, the old version keeps running.
On Android, the release is distributed through Google Play; you can check it from the updates screen in the store. Chromium-based browsers such as Edge, Brave, Opera, and Vivaldi use the same engine, so they receive the fixes on their own release schedules; you should also check the version in these browsers within a few days.
Other new features in Chrome 156
On the CSS side, the release adds the random() function; it can generate a random value in a selected range, and if you want the same value to be shared across multiple elements, you can provide a key. IndexedDB’s backend has moved to SQLite; for now, this change only covers newly created data stores. Also, because a failed module load is no longer cached, the import() call can be retried.
On Windows, Chrome’s automatic startup when the user signs in is gradually rolling out. In enterprise environments, this behavior can be disabled with the LaunchOnStartupEnabled policy.
Source: Chrome Releases · NVD

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