SecOps data connector now available for Google Workspace for Education Plus and Standard

What’s changing

We’re expanding the availability of the Google Workspace SecOps data connector to customers using Google Workspace for Education Plus and Education Standard. This feature was previously only available for our Enterprise customers.

The SecOps data connector allows you to seamlessly forward all your Google Workspace activity logs (including Gmail, Drive, Calendar, and more) into the Google SecOps platform (formerly Chronicle Security Operations).

This feature is critical for organizations, especially in the education sector, to maintain a strong security posture. By centralizing your Workspace audit data with other security telemetry, you can:

  • Enhance threat detection: Gain a unified view to correlate activity logs across your entire IT environment, making it easier to spot complex or coordinated threats like unauthorized data access, insider threats, and malicious email activity.
  • Improve incident response: Streamline your security workflows. With all data in one place, your security team can investigate incidents faster and automate responses, such as suspending compromised accounts or revoking file access.
  • Meet compliance and auditing needs: Easily maintain a long-term, searchable archive of activity logs to meet regulatory requirements and simplify internal and external audits.
This feature is a powerful, cost-effective way to utilize your existing Google Workspace data to strengthen your overall security and defense strategy.

Getting started

  • Admins: Configure the forwarding of Google Workspace audit logs to the Google SecOps platform in the Admin console. Visit the Help Center to learn more.

Rollout pace

Availability

  • This change impacts the following Google Workspace for Education Standard and Plus editions. Your organization must have an active Google SecOps subscription to utilize this data connector.

Resources

Chrome for Android Update

 Hello Everyone! We've just released Chrome 144 (144.0.7559.59) for Android to a small percentage of users. It'll become available on Google Play over the next few days. You can find more details about early Stable releases here.

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.

Krishna Govind
Google Chrome

Stable Channel Update for Desktop

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

Chrome 144.0.7559.59 (Linux) 144.0.7559.59/60 Windows/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 144.


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

[$8000][458914193] High CVE-2026-0899: Out of bounds memory access in V8. Reported by @p1nky4745 on 2025-11-08

[TBD][465730465] High CVE-2026-0900: Inappropriate implementation in V8. Reported by Google on 2025-12-03

[TBD][40057499] High CVE-2026-0901: Inappropriate implementation in Blink. Reported by Irvan Kurniawan (sourc7) on 2021-10-04

[$4000][469143679] Medium CVE-2026-0902: Inappropriate implementation in V8. Reported by 303f06e3 on 2025-12-16

[$3000][444803530] Medium CVE-2026-0903: Insufficient validation of untrusted input in Downloads. Reported by Azur on 2025-09-13

[$1000][452209495] Medium CVE-2026-0904: Incorrect security UI in Digital Credentials. Reported by Hafiizh on 2025-10-15

[TBD][465466773] Medium CVE-2026-0905: Insufficient policy enforcement in Network. Reported by Google on 2025-12-02

[$2000][467448811] Low CVE-2026-0906: Incorrect security UI. Reported by Khalil Zhani on 2025-12-10

[$500][444653104] Low CVE-2026-0907: Incorrect security UI in Split View. Reported by Hafiizh on 2025-09-12

[TBD][452209503] Low CVE-2026-0908: Use after free in ANGLE. Reported by Glitchers BoB 14th. on 2025-10-15




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

Automatic room check-in for Google Meet available on mobile devices

To simplify the process of joining meetings for those using companion mode on a phone or tablet 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 phone or tablet’s microphone to detect an ultrasound signal from the conference room hardware, streamlining the process and eliminating unnecessary steps. This feature is available on Android and iOS devices.


The "Use Companion mode" button is highlighted, prompting the user to tap it to join the call.

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 

  • Minimum Android build required: 
    • Meet: 336.0. (Android Settings > Apps > Meet > [App Info > Version])
    • Gmail: 2025.12.01. (Android Settings > Apps > Gmail > [App Info > Version])
  • Minimum iOS build required: 
    • Meet: 336.0. (Meet > Settings -> About, terms, and privacy > Version)
    • Gmail:  6.0.251201. (Settings > About Gmail > Version)

Getting started

  • Admins: Proximity detection is on by default and can be enabled or disabled at the room level. Visit the Help Center to learn more about turning proximity detection on or off.
  • 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 proximity check-in isn’t working, visit the Help Center for troubleshooting tips. Users can still check in manually after joining the call.

Rollout pace

Availability

  • Available to all Google Workspace customers, and Workspace Individual subscribers

Resources

Beta Channel Update for ChromeOS / ChromeOS Flex

The ChromeOS Beta channel is being updated to OS version 16503.46.0 (Browser version 144.0.7559.84) for most ChromeOS devices.

If you find new issues, please let us know one of the following ways:
  1. File a bug

  2. Visit our ChromeOS communities

    1. General: Chromebook Help Community

    2. Beta Specific: ChromeOS Beta Help Community

  3. Report an issue or send feedback on Chrome

  4. Interested in switching channels? Find out how.

Thanks,
Alon Bajayo
ChromeOS Release Manager