Posted March 7Mar 7 Google has officially released Chrome 140 to the stable channel for Windows, Mac, and Linux platforms, marking another significant milestone in the browser’s continuous evolution toward enhanced security and performance.The Chrome team announced on September 2, 2025, that this latest version addresses multiple critical vulnerabilities while introducing improvements that strengthen the browser’s overall architecture.Chrome 140.0.7339.80 for Linux and versions 140.0.7339.80/81 for Windows and Mac represent a comprehensive security-focused update that tackles six distinct vulnerabilities, including a high-severity use-after-free flaw in the V8 JavaScript engine.The rollout follows Google’s standard phased deployment strategy, ensuring gradual distribution over the coming days and weeks to minimize potential compatibility issues.Security Vulnerabilities and Research ContributionsThe most critical security fix addresses CVE-2025-9864, a high-severity use-after-free vulnerability in V8 discovered by Pavel Kuzmin from Yandex Security Team.This type of vulnerability occurs when a program continues to use memory after it has been freed, potentially allowing attackers to execute arbitrary code or cause system crashes.The V8 engine, which powers JavaScript execution in Chrome, represents a high-value target for security researchers due to its central role in web browsing functionality.Google’s bug bounty program continues to incentivize external security research, with the company distributing $10,000 in total rewards for four medium-severity vulnerabilities.The security researchers who contributed to this release include Khalil Zhani, who received $5,000 for identifying CVE-2025-9865 in the Toolbar implementation, and NDevTK, who earned $4,000 for discovering CVE-2025-9866 in Extensions functionality.CVE IdentifierSeverityComponentResearcherRewardDiscovery DateCVE-2025-9864HighV8 EnginePavel Kuzmin (Yandex)Not DisclosedJuly 28, 2025CVE-2025-9865MediumToolbarKhalil Zhani$5,000August 7, 2025CVE-2025-9866MediumExtensionsNDevTK$4,000November 16, 2024CVE-2025-9867MediumDownloadsFarras Givari$1,000May 4, 2025Google’s internal security initiatives continue to play a crucial role in vulnerability detection, utilizing advanced tools including AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer, and AFL (American Fuzzy Lop).These automated testing frameworks enable continuous security auditing throughout the development cycle, identifying potential vulnerabilities before they reach production environments.The extended stable channel has also received version 140.0.7339.81 for Windows and Mac platforms, providing enterprise users with additional stability testing before widespread deployment.This dual-channel approach reflects Google’s commitment to balancing rapid security response with enterprise-grade stability requirements, ensuring that critical infrastructure remains protected while minimizing operational disruption.Silent installation https://www.mediafire.com/file/euwnvsm00m1buqb/Google+Chrome+140.0.7339.81+AIO+Silent+Install.7z/filehttps://seyarabata.com/68b7fe7658d80https://mir.cr/0UB9AFMD 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 2 hours ago2 hr by T3rM1nat0Rr3
April 16Apr 16 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 RewardsNote: 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-21We 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
July 17Jul 17 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
July 31Jul 31 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 RewardsNote: 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 fixedThis 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-19We 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
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.