Google has officially rolled out a crucial update for its Chrome browser, promoting version 146 to the stable channel for Windows, Mac, and Linux users.
Many of these flaws involve deep-seated memory corruption issues that, if left unpatched, could allow remote attackers to execute arbitrary code and fully compromise affected systems.
Users are strongly advised to upgrade immediately to version 146.0.7680.71 for Linux and 146.0.7680.71/72 for Windows and Mac.
Released on March 10, 2026, this significant patch addresses 29 security vulnerabilities.
The most severe vulnerability addressed in this cycle is CVE-2026-3913, a critical heap buffer overflow located in the WebML component.
Discovered by security researcher Tobias Wienand, this highly dangerous flaw earned a $33,000 bug bounty.
Heap buffer overflows are particularly alarming because they can be exploited to crash the browser or facilitate unauthorized remote code execution (RCE).
Alongside this critical bug, the update resolves 11 high-severity vulnerabilities.
Many of these are “Use after free” (UAF) and out-of-bounds memory access errors impacting various browser components, including Web Speech, Agents, Extensions, TextEncoding, and MediaStream.
Threat actors frequently target UAF flaws because they allow attackers to manipulate memory pointers and insert malicious payloads.
The update also mitigates 17 medium and low-severity bugs in areas like the V8 JavaScript engine, PDF viewer, and developer tools.
To secure your browser against these severe threats, follow these immediate mitigation steps:
- Open Google Chrome and click the three-dot menu in the top right corner.
- Navigate to “Help” and select “About Google Chrome.”
- Allow the browser to automatically download version 146.0.7680.71 or 146.0.7680.72.
- Restart the browser to fully apply the security patches.
- Keep automatic updates enabled to ensure future security fixes are applied without delay.
Critical and High-Severity Chrome 146 Vulnerabilities
| CVE ID | Severity | Component & Vulnerability |
|---|---|---|
| CVE-2026-3913 | Critical | Heap buffer overflow in WebML |
| CVE-2026-3914 | High | Integer overflow in WebML |
| CVE-2026-3915 | High | Heap buffer overflow in WebML |
| CVE-2026-3916 | High | Out of bounds read in Web Speech |
| CVE-2026-3917 | High | Use after free in Agents |
| CVE-2026-3918 | High | Use after free in WebMCP |
| CVE-2026-3919 | High | Use after free in Extensions |
| CVE-2026-3920 | High | Out of bounds memory access in WebML |
| CVE-2026-3921 | High | Use after free in TextEncoding |
| CVE-2026-3922 | High | Use after free in MediaStream |
| CVE-2026-3923 | High | Use after free in WebMIDI |
| CVE-2026-3924 | High | Use after free in WindowDialog |
| CVE-2026-3925 | Medium | Incorrect security UI in LookalikeChecks |
| CVE-2026-3926 | Medium | Out of bounds read in V8 |
| CVE-2026-3927 | Medium | Incorrect security UI in PictureInPicture |
| CVE-2026-3928 | Medium | Insufficient policy enforcement in Extensions |
| CVE-2026-3929 | Medium | Side-channel information leakage in ResourceTiming |
| CVE-2026-3930 | Medium | Unsafe navigation in Navigation |
| CVE-2026-3931 | Medium | Heap buffer overflow in Skia |
| CVE-2026-3932 | Medium | Insufficient policy enforcement in PDF |
| CVE-2026-3934 | Medium | Insufficient policy enforcement in ChromeDriver |
| CVE-2026-3935 | Medium | Incorrect security UI in WebAppInstalls |
| CVE-2026-3936 | Medium | Use after free in WebView |
| CVE-2026-3937 | Low | Incorrect security UI in Downloads |
| CVE-2026-3938 | Low | Insufficient policy enforcement in Clipboard |
| CVE-2026-3939 | Low | Insufficient policy enforcement in PDF |
| CVE-2026-3940 | Low | Insufficient policy enforcement in DevTools |
| CVE-2026-3941 | Low | Insufficient policy enforcement in DevTools |
| CVE-2026-3942 | Low | Incorrect security UI in PictureInPicture |
