Jump 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 142.0.7444.135 Dual x86x64 Silent

Featured Replies

0766507434faa61f7693b9f97211e.jpg


Google has officially promoted Chrome 142 to the stable channel, delivering critical security updates for Windows, Mac, and Linux users.

The rollout begins immediately and will continue over the next few days or weeks, ensuring widespread protection against newly discovered threats.

This version addresses 20 vulnerabilities, many of which could enable attackers to execute malicious code remotely, potentially compromising user data and system integrity.

The update underscores Google’s commitment to rapid response in the face of evolving browser-based attacks.

Chrome 142.0.7444.59 for Linux, 142.0.7444.59/60 for Windows, and 142.0.7444.60 for Mac incorporate a range of fixes and performance improvements.

Detailed change logs are available through Chromium’s source repository, highlighting enhancements in rendering, stability, and user interface.

google

While full details on new features will appear in upcoming posts on the Chrome and Chromium blogs, the immediate priority is bolstering defenses against exploitation attempts.

Security experts recommend users enable automatic updates to mitigate risks promptly, as unpatched browsers remain prime targets for cybercriminals.

Chrome 142 Released – Fix for 20 Vulnerabilities

The update addresses a wide range of vulnerabilities, including 20 security patches. Details about the bugs will initially remain confidential to allow for global deployment and to prevent facilitating active exploits.

Several fixes arise from external researchers, earning bounties under Google’s Vulnerability Reward Program, while others result from internal audits and fuzzing tools like AddressSanitizer and libFuzzer.

High-severity issues dominate, particularly in the V8 JavaScript engine, where type confusion, race conditions, and inappropriate implementations could lead to arbitrary code execution.

Media handling and extensions also receive attention, closing gaps that might allow unauthorized access or policy bypasses. Lower-severity fixes address UI inconsistencies and storage races, preventing subtle but persistent risks.

For a breakdown of key externally reported vulnerabilities, see the table below:

CVE ID Severity Description Reporter Bounty Report Date

CVE-2025-12428 High Type Confusion in V8 Man Yue Mo (GitHub Security Lab) $50,000 2025-09-26

CVE-2025-12429 High Inappropriate implementation in V8 Aorui Zhang $50,000 2025-10-10

CVE-2025-12430 High Object lifecycle issue in Media round.about $10,000 2025-09-04

CVE-2025-12431 High Inappropriate implementation in Extensions Alesandro Ortiz $4,000 2025-08-06

CVE-2025-12432 High Race in V8 Google Big Sleep N/A 2025-08-18

CVE-2025-12433 High Inappropriate implementation in V8 Google Big Sleep N/A 2025-10-07

CVE-2025-12036 High Inappropriate implementation in V8 Google Big Sleep N/A 2025-10-15

CVE-2025-12434 Medium Race in Storage Lijo A.T $3,000 2024-04-27

CVE-2025-12435 Medium Incorrect security UI in Omnibox Hafiizh $3,000 2025-09-21

CVE-2025-12436 Medium Policy bypass in Extensions Luan Herrera (@lbherrera_) $2,000 2021-02-08

(Additional medium and low-severity fixes include use-after-free errors in PageInfo and Ozone, out-of-bounds reads in V8 and WebXR, and UI issues in Autofill, Fullscreen, and SplitView, reported by researchers like Umar Farooq, Wei Yuan, and Khalil Zhani.)

Google extends thanks to contributors who helped squash these bugs before they hit production. Internal efforts, including fuzzing and sanitizer tools, accounted for numerous fixes, preventing a wide array of potential exploits.

As browser usage surges amid rising phishing and malware campaigns, this release reinforces Chrome’s position as a secure default for billions. Users should verify updates via chrome://settings/help to stay protected.


 

Windows 11/10


Silent installation

 

https://send.now/cyk6yds0h23u

https://www.mediafire.com/file/88mcst3wu3aovle/Google+Chrome+142.0.7444.135+AIO+Silent+Install.7z/file

https://seyarabata.com/690c5b3f40f6c

 

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
  • T3rM1nat0Rr3 changed the title to Google Chrome 134.0.6998.166 Dual x86x64 Silent
  • 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
  • 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
  • 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
  • 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
  • T3rM1nat0Rr3 changed the title to Google Chrome 138.0.7204.50 Dual x86x64 Silent
  • 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
  • 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
  • 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
  • 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...

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.