Google released a new version of its Chrome web browser for desktop operating systems and Android this week. Chrome 139 is a security and feature update, but it also changes the system requirements on Android.

Desktop users can download and install the update via Menu > Help > About Google Chrome. If you are on Windows, you may also run winget upgrade google.chrome.exe to install the latest version.

Chrome 139: the security update

Google mentions on the Chrome Releases Blog that it fixed 12 unique security issues in Chrome 139.  It lists eight security issues publicly only, which have a severity rating of either medium or low.

The company makes no mention of exploits in the wild, which means that it is not aware of any targeted attacks.

Chrome 139: the new features and changes

Google introduces an AI Mode for search recommendations in Chrome 139. You may find a new section "Explore in AI Mode" when you click on the address bar or type something. This section complements the suggestions that Google Chrome displays, e.g., if bookmarks match what you type.

The feature is rolled out over time. Means: it make take days, weeks or even longer before you may see the new section.

Enterprise admins may control the feature with the policy AIModeSettings.

Other Changes in Chrome 139:

• Google Chrome 139 does not support Android Oreo or Android Pie anymore. The operating systems launched in 2017 and 2018 respectively.

• Google Chrome 139 does not support macOS 11.

• Chrome 139 on Android contacts Google servers when Android APK files are downloaded to "get a verdict about their safety". If Google determines that an APK is dangerous, it will show a warning and block the download. Users may bypass the warning to proceed with the download. The checks are performed if Standard Protection or Enhanced Protection are enabled in Google Safe Browsing.

• The Passwords and other sign-in data selection in Delete browsing data is removed. Users are redirected to the Google Password Manager instead, as it offers "better manage and delete passwords and passkeys" capabilities".

• Google removed the startup flags --extensions-on-chrome-urls and --disable-extensions-except to "mitigate the risks associated with harmful and unwanted extensions".

• Automatic fallback to WebGL backed by SwiftShader is deprecated and WebGL context creation now fails instead of falling back to SwiftShader.

• Shared tab groups continues to roll out in Chrome 139. This enables the sharing of tab groups with other users.

 https://youtu.be/9YHqUQDfOdA

 Windows 11/10

Silent installation

 

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

https://mir.cr/1UE75JVX

 

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

 

 


https://mir.cr/0GHBFW82

Edited 16 hours ago16 hr by T3rM1nat0Rr3

Google Chrome Changelog:

Google Chrome Changelog:

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

135.0.7049.115 new

Google Chrome 136.0.7103.93 update

Google Chrome 136.0.7103.114 update

137.0.7151.56 update

Google Chrome 137.0.7151.69 update

Google Chrome 137.0.7151.120 updates

Google Chrome 138.0.7204.50 update

https://developer.chrome.com/release-notes/138

  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

138.0.7204.169  Update

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