Chrome for Android Update

Hi, everyone! We've just released Chrome 139 (139.0.7258.62) 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 releases (Windows & Mac: 139.0.7258.66/67, Linux: 139.0.7258.66) unless otherwise noted.


Harry Souders
Google Chrome

Extended Stable Updates for Desktop

The Extended Stable channel has been updated to 138.0.7204.224 for Windows and 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

Stable Channel Update for Desktop

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

Chrome 139.0.7258.66 (Linux)  139.0.7258.66/67 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 139.

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 12 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information.


[$2000][414760982] Medium CVE-2025-8576: Use after free in Extensions. Reported by asnine on 2025-04-30

[$1000][384050903] Medium CVE-2025-8577: Inappropriate implementation in Picture In Picture. Reported by Umar Farooq on 2024-12-14

[TBD][423387026] Medium CVE-2025-8578: Use after free in Cast. Reported by Fayez on 2025-06-09

[$10000][407791462] Low CVE-2025-8579: Inappropriate implementation in Gemini Live in Chrome. Reported by Alesandro Ortiz on 2025-04-02

[$2000][411544197] Low CVE-2025-8580: Inappropriate implementation in Filesystems. Reported by Huuuuu on 2025-04-18

[$2000][416942878] Low CVE-2025-8581: Inappropriate implementation in Extensions. Reported by Vincent Dragnea on 2025-05-11

[$1000][40089450] Low CVE-2025-8582: Insufficient validation of untrusted input in DOM. Reported by Anonymous on 2017-10-31

[$500][373794472] Low CVE-2025-8583: Inappropriate implementation in Permissions. Reported by Shaheen Fazim on 2024-10-16


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:

  • [436398554] 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

Upcoming changes to reboot, alert, and log settings for Google Meet hardware devices


What’s changing 

In the coming weeks, we will introduce changes to multiple settings in Google Meet hardware admin console that will offer new capabilities and a better experience for admins. These changes will impact the following settings: 
  • Alert configuration 
  • Time zone 
  • Log upload settings & Device state reporting 
  • Scheduled reboot 
While rolling out the new changes, there will be a 2-3 week period where both the new setting and old setting will be displayed. During this time, admins will see a banner in the admin console indicating this, as well as a banner indicating your previous configuration is being migrated. 

Alert configuration: 
Alerts will be more streamlined with a separate setting for Email alerts and SMS alerts. There will be one checkbox per SMS and per email alert. Options to select alerts for missing microphone, missing default camera, and other device and peripheral issues will be displayed for both email and text message alerts. 


The existing Alerts experience 


The updated, streamlined Alerts experience 


Time zone: 
We have simplified the time zone setting so it’s more customizable. The new time zone options allow admins to use the time zone configured during setup for their devices, manually select the time zone, use the device IP address, or location to detect the time zone. Note: Devices not running on ChromeOS are not supported by this feature.


The existing Time zone experience 


The updated, streamlined Time zone experience 


Log Upload Settings & Device State Reporting: 
Currently, there are three separate settings in the Admin console which control whether error reports, metrics, and logs are uploaded for troubleshooting purposes: 
  • Report diagnostics > Send Google usage metrics and logs to improve meeting room hardware 
  • Logs and feedback > Send Google usage metrics and logs periodically and after each meeting for troubleshooting purposes 
  • Error reporting > Send error reports to Google 
Going forward, this will be controlled by one unified setting found under Google Meet Hardware > Settings > Data Sharing. This update provides a more straightforward, easy to understand experience for Admins. 


The existing Log Upload Settings & Device State Reporting 


The updated Log Upload Settings & Device State Reporting 



Since we’re consolidating three separate settings into one, your previous selections will determine the default ON/OFF state for the new setting: 
  • If you have ANY of the three original settings disabled, the new unified setting will be OFF by default. 
  • If you have ALL three of the original settings enabled, the new unified setting will be ON by default. 
Additionally, the device state reporting will now be enabled for all Google Meet Hardware customers. Device state reporting provides essential insights for Google Meet hardware admins to actively manage GMH deployments, including device health, network connectivity to facilitate troubleshooting, proactive maintenance, and informed decision-making. 

Scheduled Reboot: 
Currently, you can set reboots to occur at a frequency (between 1-7 days). Soon, you'll be able to select specific days of the week for reboots. This change will make scheduled reboots happen more predictably. 


The existing Scheduled Reboot 


The Updated Scheduled Reboot 


We recommend that you review your settings to make sure you know when your devices will reboot. If you take no action on your reboot settings, they will be migrated as follows: 



Reboot Frequency
(Old Setting)		       Day
      (New Setting)
1     Daily
2, 3, 4, 5, 6     Monday, Thursday
7     Monday

Additional details 

Audit logs for all of the new simplified settings outlined in this post can be found under “Change application setting”. Legacy settings will continue to generate audit logs under the “Chromebox for meetings Device Setting Change” event until they are removed from the user interface. 

Getting started 


Rollout pace 

  • Rapid and Scheduled Release domains: Gradual rollout (up to 15 days for feature visibility) starting August 5, 2025 

Availability 

  • Available to all Google Workspace customers with Google Meet hardware devices

Resources 

Automatic Room Check-in in Google Meet with Proximity Detection

What’s changing

To simplify the process of joining meetings for those using companion mode on laptops within a conference room, we’re introducing automatic room check-in via ultrasound proximity detection. To automatically check you in, the green room uses your laptop’s microphone to detect an ultrasound signal from the conference room hardware, streamlining the process and eliminating unnecessary steps.

The “Use Companion mode” button is highlighted, prompting the user to click it to join the call.

Who’s impacted

  • Admins and end users

Why it’s important

To simplify joining meetings from a conference room and prevent disruptive audio feedback, Google Meet now intelligently guides you to the best joining option.
Meet intelligently knows when you are in a room using an ultrasonic signal, and highlights the “Use Companion mode” button before you even join the call. This wayfinding feature helps ensure a seamless, echo-free start to your meeting. When you join using the highlighted Companion mode button, you will also be automatically checked into the correct room. 

Additional Details

  • Improving Room Check-in from Greenroom: Today, when at least one Google Meet hardware device is on the call and the user clicks on “Use companion mode,” Meet will present an option to check-in to the room. Room Check-in by proximity will replace this experience.
  • Platform & Browser: Only supported on Meet web (meet.google.com) for Chrome. 
  • Supported pages: Proximity detection is limited to a call’s greenroom and a brief period after joining companion mode
  • Unsupported pages: Proximity detection will not function on g.co/present or g.co/companion. However, it will detect once the user joins companion mode for a brief period after joining.
  • Google Meet hardware peripherals: We have tested and verified functionality only with certified peripheral devices. While other devices might work, they are not officially supported and we cannot guarantee their performance. 

Getting started

  • Admins: 
    • A “Proximity Detection” device setting will be available in the Admin console to better support needs of each organization. Admins have granular controls to enable or disable proximity detection on specific Google Meet hardware devices.
    • Proximity Detection is on by default. This feature will be automatically enabled on all Google Meet hardware devices. If you need to change this setting:

  • End users: 
    • The Companion mode entry point will be highlighted in the greenroom when the proximity detection signal is detected. 
    • After joining a meeting in Companion mode, the user will be automatically checked into the room. If you have dynamic tiles enabled you will also be prompted to use Face Match to identify your face so your Dynamic tile shows your name instead of the room name.
    • Proximity check-in not working? See the help documentation for troubleshooting tips. You can still check in manually after joining the call.

The companion mode entry point is highlighted to inform the user that the meeting room for this call has been detected.

Rollout pace

Availability

  • Available to all Google Workspace customers with Google Meet hardware devices

Resources