Stable Channel Update for ChromeOS / ChromeOS Flex

The Stable channel is being updated to 125.0.6422.140 (Platform version: 15853.53.0) for most ChromeOS devices and will be rolled out over the next few days.

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

Interested in switching channels? Find out how.

Chrome Browser release notes can be found here.

Matt Nelson
Google ChromeOS

Chrome for Android Update

  Hello, Everyone! We've just released Chrome 125 (125.0.6422.146/.147) 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: 125.0.6422.141/.142 and Linux:125.0.6422.141 ) unless otherwise noted.

Krishna Govind
Google Chrome

Extended Stable Channel Update for Desktop

The Extended Stable channel has been updated to 124.0.6367.243 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.


Daniel Yip
Google Chrome

Stable Channel Update for Desktop

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


[$7000][339877165] High CVE-2024-5493: Heap buffer overflow in WebRTC. Reported by Cassidy Kim(@cassidy6564) on 2024-05-11

[TBD][338071106] High CVE-2024-5494: Use after free in Dawn. Reported by wgslfuzz on 2024-05-01

[TBD][338103465] High CVE-2024-5495: Use after free in Dawn. Reported by wgslfuzz on 2024-05-01

[TBD][338929744] High CVE-2024-5496: Use after free in Media Session. Reported by Cassidy Kim(@cassidy6564) on 2024-05-06

[TBD][339061099] High CVE-2024-5497: Out of bounds memory access in Browser UI. Reported by zh1x1an1221 of Ant Group Tianqiong Security Lab on 2024-05-07

[TBD][339588211] High CVE-2024-5498: Use after free in Presentation API. Reported by anymous on 2024-05-09

[TBD][339877167] High CVE-2024-5499: Out of bounds write in Streams API. Reported by anonymous on 2024-05-11


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:

  • [343518382] 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.




Prudhvikumar Bommana

Google Chrome

Launching Structured Data Files QA format and v7.1

Today we’re announcing the general availability of the Structured Data Files (SDF) v7.1 and the open beta of our new QA format. Both are available to all Display & Video 360 users.

While in open beta, the QA format might be updated without notice. These updates will be reflected in the documentation. We will announce the QA format release to general availability at a later date.

What’s new in v7.1?

All users can now use SDF v7.1 to upload and download SDFs in the Display & Video 360 UI, and to download SDFs through the Display & Video 360 API.

The update from v7 to v7.1 includes the following changes:

  • Added new TrueView Video Ad settings to the Line Item resource.
  • Renamed three insertion order columns to use “Kpi” instead of “Performance Goal.”
  • Introduced a new objective column to the insertion order resource. This column is currently in beta and only available to participating clients.

Full details on the changes made in v7.1 can be found in our Structured Data Files release notes. If you are currently using SDF v5.5 or v6, follow the instructions on our v7 migration guide first before migrating to v7.1.

What’s the SDF QA format?

The new SDF QA format provides SDFs with human-readable data to make it easier to review Display & Video 360 resource settings in bulk.

All supported SDF versions offer this format through two new file types: Line Item - QA and YouTube Ad Group - QA. These file types provide the same information as standard format files of the same version, and convey a subset of that information using display name values instead of numeric IDs.

SDF QA files are read-only and cannot be uploaded to modify or create Display & Video 360 resources. Currently, QA format files are only available through the Display & Video 360 interface.

We are accepting feedback on the QA format while it is in open beta. To submit feedback, please use the Send Feedback button on the relevant reference documentation page. We will consider suggested updates before releasing the QA format to general availability.

If you run into issues or need help with this new format or version, please follow the instructions on our support guide or contact us using our contact form.

- Trevor Mulchay, Display & Video 360 API Team

Chrome Stable for iOS Update

Hi everyone! We've just released Chrome Stable 125 (125.0.6422.145) for iOS; it'll become available on App Store in the next few hours.

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

The Calendar API now distinguishes events created from Gmail

What’s changing

Starting May 30, 2024, the Calendar API will distinguish events created from Gmail. New and existing events from Gmail that are scheduled for a future date will:

In Google Calendar clients events from email may be rendered slightly differently to regular events and show a link back to the original email:



Google Calendar limits edits for events from email:



Additional details

If you’re using the Calendar API, we recommend the following to help avoid any disruptions in your applications:
  • Ensure that your code does not apply restricted updates to events with the type “fromGmail”.
    • Temporarily, updates on events with the type “fromGmail” are restricted to the properties reminders, colorId, visibility, status, and extendedProperties. Stay tuned to the Workspace updates blog for more information.
    • Review your code if it filters by eventType for Events.list or Events.watch. Filtering by eventType “default” will no longer return events extracted from emails.

Getting started


Rollout pace