Skip to content
View in the app

A better way to browse. Learn more.

WinCert.net Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Google Chrome 154.0.8037.58 Dual x86x64 Silent

Featured Replies

1787121181-chrome.jpg

Google released Chrome 154 on Tuesday bringing with it patches for 108 vulnerabilities, which included 11 critical-severity bugs. The update brings the build version of Windows and Linux to 154.0.8037.57, while Chrome on macOS is updated to 154.0.8037.57. Users should get this update in the coming days.

The patches in this update focus heavily on memory safety, including critical bugs across graphics and execution engines such as ANGLE buffer overflow (CVE-2026-95350). This bug carried a $5,000 bounty, which was awarded to STAR Labs SG researchers. Another $2,500 was issued for CVE-2026-95357 which was an out of bounds write in GPU reported by Anymous.

Other high-severity patches targeted type confusions and out-of-bounds writes in the V8 JavaScript engine. Some of these issues were flagged by internal sanitizers and external audits from entities such as OpenAI Codex Security.

End users can either wait for their browser to update silently in the background, or force the installation immediately. If you do not want to wait, press the three-dot menu at the top right then go to Help > About Google Chrome. On Windows and macOS, the browser will automatically download the update when you open this page. On Linux, you need to check for updates in your update manager.

Keeping software up to date has become more important than ever before. With public access to powerful artificial intelligence, it is easier than ever before for malicious actors to exploit bugs in software. To ensure users get fixes more quickly, software like Google Chrome, Firefox, and even Visual Studio Code have moved to much faster release cycles. In the case of Google Chrome, version 155 will be released in just two weeks.

One area of difficulty has been Windows Patch Tuesday updates. These updates generally introduce some annoying regressions, however, thanks to AI, they have introduced almost a thousand fixes per release. This makes it very dangerous for users to skip over these updates.

Windows 11/10


Silent installation

 

https://www.mediafire.com/file/qcq8ld2ihwm0c66/Google+Chrome+154.0.8037.58+AIO+Silent+Install.7z/file

https://transfer.it/t/LX6WUFwzQJhL

 

Windows 7/8


Silent installation

 

Google Chrome 109.0.5414.168 AIO windows 7 last version Install Silent 


https://www.mediafire.com/file/y480s6kyzu9k81l/Google+Chrome+109.0.5414.168+AIO+Install+Silent.7z/file


Edited by T3rM1nat0Rr3

  • T3rM1nat0Rr3 changed the title to Google Chrome 134.0.6998.89 Dual x86x64 Silent
  • Replies 58
  • Views 40.2k
  • Created
  • Last Reply

Top Posters In This Topic

  • T3rM1nat0Rr3 changed the title to Google Chrome 134.0.6998.166 Dual x86x64 Silent
  • 2 weeks later...
  • T3rM1nat0Rr3 changed the title to Google Chrome 134.0.6998.178 Dual x86x64 Silent
  • T3rM1nat0Rr3 changed the title to Google Chrome 135.0.7049.42 Dual x86x64 Silent
  • T3rM1nat0Rr3 changed the title to Google Chrome 135.0.7049.96 Dual x86x64 Silent
  • 2 weeks later...
  • Author

The Stable channel has been updated to 135.0.7049.95/.96 for Windows, Mac and 135.0.7049.95 for Linux which will roll out over the coming days/weeks. A full list of changes in this build is available in the Log.

Security Fixes and Rewards

Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed.


This update includes 2 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information.

[TBD][409619251] Critical CVE-2025-3619: Heap buffer overflow in Codecs. Reported by Elias Hohl on 2025-04-09

[TBD][405292639] High CVE-2025-3620: Use after free in USB. Reported by @retsew0x01 on 2025-03-21

We would also like to thank all security researchers that worked with us during the development cycle to prevent security bugs from ever reaching the stable channel.

Many of our security bugs are detected using AddressSanitizer, MemorySanitizer,UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer, or AFL.

 Interested in switching release channels? Find out how here. If you find a new issue, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.

PrudhviKumar Bommana Google Chrome

  • T3rM1nat0Rr3 changed the title to Google Chrome 135.0.7049.115 Dual x86x64 Silent
  • T3rM1nat0Rr3 changed the title to Google Chrome 136.0.7103.93 Dual x86x64 Silent
  • 3 weeks later...
  • T3rM1nat0Rr3 changed the title to Google Chrome 136.0.7103.114 Dual x86x64 Silent
  • T3rM1nat0Rr3 changed the title to Google Chrome 137.0.7151.56 Dual x86x64 Silent
  • 2 weeks later...
  • T3rM1nat0Rr3 changed the title to Google Chrome 137.0.7151.69 Dual x86x64 Silent
  • T3rM1nat0Rr3 changed the title to Google Chrome 137.0.7151.120 Dual x86x64 Silent
  • 2 weeks later...
  • T3rM1nat0Rr3 changed the title to Google Chrome 138.0.7204.50 Dual x86x64 Silent
  • 2 weeks later...
  • T3rM1nat0Rr3 changed the title to Google Chrome 138.0.7204.97 Dual x86x64 Silent
  • T3rM1nat0Rr3 changed the title to Google Chrome 138.0.7204.158 Dual x86x64 Silent
  • 3 weeks later...
  • Author

  Hi, everyone! We've just released Chrome 138 (138.0.7204.157) for Android. It'll become available on Google Play over the next few days. 

This release includes stability and performance improvements. You can see a full list of the changes in the Git log. If you find a new issue, please let us know by filing a bug.

Android releases contain the same security fixes as their corresponding Desktop (Windows & Mac: 138.0.7204.157/158, Linux: 138.0.7204.157) unless otherwise noted.

Krishna Govind

  • T3rM1nat0Rr3 changed the title to Google Chrome 138.0.7204.169 Dual x86x64 Silent
  • T3rM1nat0Rr3 changed the title to Google Chrome 138.0.7204.184 Dual x86x64 Silent
  • Author

The Stable channel has been updated to 138.0.7204.183/.184 for Windows, Mac and 138.0.7204.183 for Linux which will roll out over the coming days/weeks. A full list of changes in this build is available in the Log.

Security Fixes and Rewards

Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed

This update includes4security fixes. Below, we highlight fixes that were contributed by external researchers. Please see theChrome Security Pagefor more information.

[$8000][
426054987] High CVE-2025-8292: Use after free in Media Stream. Reported by Anonymous on 2025-06-19


We would also like to thank all security researchers that worked with us during the development cycle to prevent security bugs from ever reaching the stable channel.

As usual, our ongoing internal security work was responsible for a wide range of fixes:

[
434760450] Various fixes from internal audits, fuzzing and other initiatives

  • T3rM1nat0Rr3 changed the title to Google Chrome 139.0.7258.67 Dual x86x64 Silent
  • 2 weeks later...
  • T3rM1nat0Rr3 changed the title to Google Chrome 139.0.7258.139 Dual x86x64 Silent
  • T3rM1nat0Rr3 changed the title to Google Chrome 139.0.7258.155 Dual x86x64 Silent
  • T3rM1nat0Rr3 changed the title to Google Chrome 140.0.7339.81 Dual x86x64 Silent
  • T3rM1nat0Rr3 changed the title to Google Chrome 140.0.7339.214 Dual x86x64 Silent
  • 4 weeks later...
  • Author

The Stable channel has been updated to 140.0.7339.213/.214 for Mac, which will roll out over the coming days/weeks. A full list of changes in this build is available in the Log.

Interested in switching release channels? Find out how here. If you find a new issue, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.


Srinivas Sista
Google Chrome

  • T3rM1nat0Rr3 changed the title to Google Chrome 141.0.7390.55 Dual x86x64 Silent
  • Author

The Chrome team is delighted to announce the promotion of Chrome 141 to the stable channel for Windows, Mac and Linux. This will roll out over the coming days/weeks.

Chrome 141.0.7390.54 (Linux) 141.0.7390.54/55 Windows and Mac contains a number of fixes and improvements -- a list of changes is available in the log. Watch out for upcoming Chrome and Chromium blog posts about new features and big efforts delivered in 141.

Security Fixes and Rewards

Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed.


This update includes 21 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information.


[$25000][442444724] High CVE-2025-11205: Heap buffer overflow in WebGPU. Reported by Atte Kettunen of OUSPG on 2025-09-02

[$4000][444755026] High CVE-2025-11206: Heap buffer overflow in Video. Reported by Elias Hohl on 2025-09-12

[$5000][428189824] Medium CVE-2025-11207: Side-channel information leakage in Storage. Reported by Alesandro Ortiz on 2025-06-27

[$3000][397878997] Medium CVE-2025-11208: Inappropriate implementation in Media. Reported by Kevin Joensen on 2025-02-20

[$3000][438226517] Medium CVE-2025-11209: Inappropriate implementation in Omnibox. Reported by Hafiizh on 2025-08-13

[$3000][440523110] Medium CVE-2025-11210: Side-channel information leakage in Tab. Reported by Umar Farooq  on 2025-08-22

[$3000][441917796] Medium CVE-2025-11211: Out of bounds read in Media. Reported by Kosir Jakob on 2025-08-29

[$2000][420734141] Medium CVE-2025-11212: Inappropriate implementation in Media. Reported by Ameen Basha M K on 2025-05-28

[$1000][443408317] Medium CVE-2025-11213: Inappropriate implementation in Omnibox. Reported by Hafiizh on 2025-09-06

[N/A][439758498] Medium CVE-2025-11215: Off by one error in V8. Reported by Google Big Sleep on 2025-08-19

[$1000][419721056] Low CVE-2025-11216: Inappropriate implementation in Storage. Reported by Farras Givari on 2025-05-23

[N/A][439772737] Low CVE-2025-11219: Use after free in V8. Reported by Google Big Sleep on 2025-08-19


We would also like to thank all security researchers that worked with us during the development cycle to prevent security bugs from ever reaching the stable channel.

As usual, our ongoing internal security work was responsible for a wide range of fixes:

  • [448476731] Various fixes from internal audits, fuzzing and other initiatives


Many of our security bugs are detected using
AddressSanitizer, MemorySanitizer,UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer, or AFL.

Interested in switching release channels? Find out how here. If you find a new issue, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.


Srinivas Sista

Google Chrome

  • T3rM1nat0Rr3 changed the title to Google Chrome 141.0.7390.66 Dual x86x64 Silent
  • T3rM1nat0Rr3 changed the title to Google Chrome 141.0.7390.77 Dual x86x64 Silent
  • Author

The Stable channel has been updated to 141.0.7390.76/.77 for Windows and Mac and 141.0.7390.76 for Linux, which will roll out over the coming days/weeks. A full list of changes in this build is available in the Log.


Interested in switching release channels? Find out how here. If you find a new issue, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.