March 7, 2025Mar 7 Google has fixed 10 security vulnerabilities in Chrome versions 144.0.7559.59/60 for Windows and macOS and 144.0.7559.59 for Linux. According to Google, none of these vulnerabilities have been exploited for attacks in the wild so far.What’s new in Chrome 144?In the Chrome Releases blog post, Srinivas Sista lists the 10 security vulnerabilities that have been fixed, all of which were reported to Google by external researchers (with Google apparently counting itself among them in two cases). Google classifies 3 vulnerabilities as high risk, 4 as medium risk, and the rest as low risk.Google prominently advertises the ability to have text read aloud on the web, but this was already a new feature in Chrome 143. The same applies to the feature for splitting the browser window to display two pages side by side in the same tab. AI integration continues to advance in Chrome, albeit less intrusively than in some other browsers.Chrome usually updates automatically when a new version is available. You can manually trigger the update check via Help > About Google Chrome. Google has also released Chrome for Android 144.0.7559.59 and Chrome for iOS 144.0.7559.85, with the Android version addressing the same vulnerabilities as the desktop versions. The Extended Stable Channel for Windows and macOS now also includes Chromium version 144.0.7559.60. Google plans to release Chrome 145 in early February.Four vulnerabilities received “High” severity classifications, four were rated “Medium,” and two as “Low” risk. Security researchers and bug bounty participants received compensation ranging from $500 to $8,000 for their contributions to the vulnerability disclosure process.CVE IDSeverityComponentDescriptionReporterDateRewardCVE-2026-0899HighV8Out of bounds memory access@p1nky47452025-11-08$8,000CVE-2026-0900HighV8Inappropriate implementationGoogle2025-12-03TBDCVE-2026-0901HighBlinkInappropriate implementationIrvan Kurniawan (sourc7)2021-10-04TBDCVE-2026-0902MediumV8Inappropriate implementation303f06e32025-12-16$4,000CVE-2026-0903MediumDownloadsInsufficient validation of untrusted inputAzur2025-09-13$3,000CVE-2026-0904MediumDigital CredentialsIncorrect security UIHafiizh2025-10-15$1,000CVE-2026-0905MediumNetworkInsufficient policy enforcementGoogle2025-12-02TBDCVE-2026-0906LowUIIncorrect security UIKhalil Zhani2025-12-10$2,000CVE-2026-0907LowSplit ViewIncorrect security UIHafiizh2025-09-12$500CVE-2026-0908LowANGLEUse after freeGlitchers BoB 14th.2025-10-15TBDOther Chromium-based browsersThe manufacturers of other Chromium-based browsers are now required to follow suit with their own updates. Microsoft Edge, Brave, and Vivaldi are at the security level Chrome was at prior to this update.Opera caught up with the others a week ago with the release of version 126 based on Chromium 142, but is still one Chromium update behind. Once the Extended Stable Channel for Chromium 142 comes to an end, Opera will be on its own again. Windows 11/10Silent installation https://www.mediafire.com/file/30ic1yc257l3dbc/Google+Chrome+144.0.7559.60+AIO+Silent+Install.7z/filehttps://krakenfiles.com/view/YDAj0XLbbo/file.html Windows 7/8Silent 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 3 hours ago3 hr by T3rM1nat0Rr3
April 16, 2025Apr 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 17, 2025Jul 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 31, 2025Jul 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
September 27, 2025Sep 27 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 SistaGoogle Chrome
October 2, 2025Oct 2 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 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 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-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:[448476731] Various fixes from internal audits, fuzzing and other initiativesMany 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 SistaGoogle Chrome
October 10, 2025Oct 10 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.