Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Chrome 126 received multiple security updates, not just one launch build. Google’s June 11, 2024 stable release fixed 21 security issues, including memory-safety defects in V8, Dawn and Tab Groups. Follow-up Chrome 126 updates on June 24 and July 16 fixed additional vulnerabilities. If you are checking a historical installation, the exact build number matters; current Chrome users should install the stable update offered by Google rather than seek an obsolete Chrome 126 installer.
What did the Chrome 126 update patch?
The June 11, 2024 desktop release addressed 21 security issues. Google’s notes named defects across components including V8, Dawn, Tab Groups, PDFium, audio and the memory allocator. Several publicly disclosed issues were memory-safety bugs: errors involving how software handles memory that may cause crashes and, depending on exploitability and security mitigations, could potentially enable code execution. Google’s release notes did not say that the listed vulnerabilities were being exploited in the wild.
Google said the stable rollout would take place over the following days and weeks. The initial desktop builds were 126.0.6478.54 for Linux and 126.0.6478.56 or 126.0.6478.57 for Windows and Mac. Google’s June 11 stable-channel announcement describes that release.
Which memory-safety vulnerabilities were named?
Among the issues publicly listed in the June 11 release were high-severity V8 type-confusion bugs CVE-2024-5830, CVE-2024-5833 and CVE-2024-5838; high-severity Dawn use-after-free bugs CVE-2024-5831 and CVE-2024-5832; and a high-severity heap buffer overflow in Tab Groups, CVE-2024-5835. Google also listed CVE-2024-5839, a medium-severity memory-allocator issue. These are memory-safety or memory-adjacent defects; the available release descriptions do not establish exploitability for a particular configuration.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
#1 Best Overall
Google notes that security bugs can be found with tools including AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer and AFL. That statement describes detection methods generally; it does not identify which tool found each Chrome 126 issue. Some Chromium bug details may remain restricted while users update.
Chrome 126 security updates by release
The 126 branch received later security fixes after its initial stable release. The counts below are the totals stated in Google’s release posts for each update; they are not a count of memory-safety issues alone.
| Release date | Desktop versions | Security fixes stated | Publicly named examples |
|---|---|---|---|
| June 11, 2024 | Linux 126.0.6478.54; Windows and Mac 126.0.6478.56/57 | 21 | V8 type confusion, Dawn use after free, Tab Groups heap buffer overflow, and a memory-allocator issue. Google release post |
| June 24, 2024 | Linux 126.0.6478.126; Windows and Mac 126.0.6478.126/127 | 5 | High-severity use-after-free bugs in Dawn (CVE-2024-6290, CVE-2024-6292 and CVE-2024-6293) and SwiftShader (CVE-2024-6291). Google release post |
| July 16, 2024 | Linux 126.0.6478.182; Windows and Mac 126.0.6478.182/183 | 10 | High-severity out-of-bounds memory access in V8 (CVE-2024-6779), and use-after-free bugs in Screen Capture (CVE-2024-6774), Media Stream (CVE-2024-6775) and Audio (CVE-2024-6776). Google release post |
The milestone notes cover Android, ChromeOS, Linux, macOS and Windows, but the build numbers above are desktop versions. Do not use a desktop version number to infer the installed version on another platform.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How to tell whether a Chrome 126 installation received later fixes
For a historical desktop installation, compare its version with the applicable platform version in the table. The July 16 branch update is the latest Chrome 126 desktop update covered here. A version earlier than the listed July build does not include that branch update based on its version number; this comparison does not establish whether a system received fixes through another channel or distribution.
Free tools Windows power users keep installed
One-click scans. No signup required.
Quick Recap
Best Value
- In Chrome, open the three-dot menu and choose Help > About Google Chrome.
- Read the version shown on that page and compare it with the row for your operating system. Chrome checks for updates there and prompts you to relaunch when one is ready.
- If you still use an old Chrome 126 installation, update through the browser or your organization’s supported software channel. For ordinary current use, install the stable update currently offered by Google instead of looking for Chrome 126.
What the release notes do not establish
- Google’s cited posts list vulnerabilities and fixes but do not claim active exploitation of these CVEs.
- A vulnerability class such as use after free or type confusion describes a software defect; it does not, by itself, prove a working exploit or a particular impact on every device.
- Google may restrict details of some Chromium issues until most users have updated, so the public release notes do not necessarily describe every affected configuration or technical detail.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
