Chrome for Android Update

 Hi, everyone! We've just released Chrome 144 (144.0.7559.90) 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: 144.0.7559.96/.97, Linux: 144.0.7559.96) unless otherwise noted.


Harry Souders
Google Chrome

Stable Channel Update for Desktop

The Stable channel has been updated to 144.0.7559.96/.97 for Windows/Mac  and 144.0.7559.96 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 1 security fix. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information.


[TBD][473851441] High CVE-2026-1220: Race in V8. Reported by @p1nky4745 on 2026-01-07


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.


Srinivas Sista
Google Chrome

View Google Meet usage metrics in Gemini reports dashboard

Admins can now access usage metrics for Google Meet within the organization-level Gemini reports dashboard, in the “Gemini usage per interaction” section. This update gives you visibility into the value your organization derives from Gemini in Meet.

Specifically, the reported metrics include:

  • Usage: The number of times where Gemini was actively used in meetings, such as usage for features like “Take notes for me” or “Ask Gemini in Meet”
  • Users: The number of unique users who actively used Gemini in meetings
Visit the Help Center for more information on active usage.


This update also ensures greater accuracy in active usage metrics for Google Meet. Given this, you may see updated metrics reported for 28D active users and overall usage of Meet. 

Getting started

  • Admins: There is no admin control for this feature. Visit the Help Center to learn more about Gemini reports.
  • End users: There is no end user impact or action required.

Rollout pace

Availability

Available for Google Workspace:

  • Business Starter, Standard, and Plus
  • Enterprise Starter, Standard, and Plus
  • Essentials Starter, Enterprise Essentials, and Enterprise Essentials Plus
  • Frontline Starter, Standard, Plus
  • Individual
Also available to: 

  • Google AI Pro and Ultra
  • Google AI Ultra for Business add-on
  • Google AI Pro for Education add-on

Forward messages in Google Chat

To make it easier to share information across different conversations, we’re introducing the ability to forward messages in Google Chat. This new feature  eliminates the need for manual workarounds such as  copying and pasting text or sharing screenshots.

This feature helps improve team collaboration through: 

  • Simplified sharing: Users can quickly share information between various direct messages and spaces, without clunky workflows.
  • Context preservation: Forwarded messages display the original sender, source, and any attachments instantly; recipients can view this content even if they are not members of the original conversation.
  • Enhanced visibility: Messages forwarded from a thread can be moved into the main conversation stream, ensuring they get necessary attention.

At this time, users cannot forward messages

  • From entirely internal conversations to conversations that include users from other organizations, and
  • From conversations that include users from external organizations to other conversations that include users from external organizations
Users can, however, forward messages from conversations with people outside their organization to conversations entirely with people inside their organization.
Note that when users forward a message from a DM or group DM, a reminder to protect sensitive information will appear.

Getting started

  • Admins: There is no admin control for this feature.
  • End users: To forward a message, select "Forward message" from the message action list and choose your target conversation. Visit the Help Center to learn more about message forwarding in Chat.

Rollout pace

Availability

  • Available to all Google Workspace customers, Workspace Individual subscribers, and users with personal Google accounts

Resources

  • Google Help: Forward a message in Google Chat

Increasing flexibility when rebooting Google Meet hardware with "Reboot when idle"

What’s changing

We’re introducing more flexible control for administrators to reboot Google Meet hardware devices from the Admin console.

Previously, admins could only trigger an immediate reboot, which required careful timing to avoid disrupting ongoing meetings or device activity. Going forward, we are adding a “Reboot when idle” option. This feature gives admins the ability to reboot devices without worrying about interrupting users, as the system intelligently waits for the device to become inactive before initiating the restart.

The device is considered “in use” if it is:

  • Connected to a Google Meet, interoperability, or livestream call.
  • Presenting content via HDMI.
  • Engaged in an add-on activity (e.g., a whiteboard session).
Admins will now see two options when initiating a reboot:

  • Reboot when the device becomes idle: Queues the reboot to occur only when all user activity has ceased.
  • Reboot now, even if the device is in use: Forces an immediate reboot, overriding current activities.

Admins can now choose to wait for device inactivity before rebooting.

Getting started

Rollout pace

Availability

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

Resources

Neat now a certified Google Meet hardware partner

Google Meet is committed to helping organizations bridge the gap between distributed teams with hardware that is easy to deploy, manage, and use. Today, we’re excited to announce that Neat has joined the Google Meet hardware ecosystem as a certified partner, bringing more variety and specialized video conferencing technology to Google Workspace customers. Newly certified devices include:

  • Neat Bar Generation 2: A compact, all-in-one device optimized for huddle spaces and small to medium rooms
  • Neat Bar Pro: A high-performance solution for larger spaces, supporting multiple screens and advanced zoom capabilities
  • Neat Pad: A dedicated touch screen that serves as both a meeting controller and a room scheduling display
This new partnership expands our portfolio of certified devices, ensuring that IT teams have the flexibility to choose the hardware that best fits their unique office layouts while maintaining the native Google Meet experience users expect.

Getting started

  • Admins: Administrators do not need to take any action. If a Neat Bar Generation 2, Neat Bar Pro, or Neat Pad have been set up, it will automatically appear as a supported device within the admin console. Furthermore, these Neat devices will provide the same level of telemetry data as other AOSP-certified hardware.

Rollout pace

Availability

  • Available to all Google Workspace customers with Google Meet hardware devices. Neat devices certified for Google Meet are available for purchase through Neat’s global sales channels and authorized resellers.

Resources