Find more sustainable ways to get around, with new Maps and Search updates
Source: Search
How brands can get the most out of YouTube Shorts ads
Source: Google Ads & Commerce
Long Term Support Channel Update for ChromeOS
LTS-120 is being updated in the LTS channel to 120.0.6099.308 (Platform Version: 15662.104.0) for most ChromeOS devices. Want to know more about Long Term Support? Click here.
330575496 High 2024-2886 Use after free in WebCodecs
Source: Google Chrome Releases
Chrome Dev for Desktop Update
The Dev channel has been updated to 125.0.6420.3 for Windows, Mac and Linux.
A partial list of changes is available in the Git log. Interested in switching release channels? Find out how. 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.
Prudhvi Bommana
Google Chrome
Source: Google Chrome Releases
Chrome for Android Update
Hello, Everyone! We've just released Chrome 124 (124.0.6367.54) 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.
Source: Google Chrome Releases
Stable Channel Update for Desktop
The Stable channel has been updated to 124.0.6367.60/.61 for Windows and Mac and 124.0.6367.60 to Linux which will roll out over the coming days/weeks. A full list of changes in this build is available in the Log.
The Extended Stable channel has been updated to 124.0.6367.60/.61 for Windows and Mac which will roll out over the coming days/weeks.
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 22 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information.
[$20000][331358160] High CVE-2024-3832: Object corruption in V8. Reported by Man Yue Mo of GitHub Security Lab on 2024-03-27
[$10000][331383939] High CVE-2024-3833: Object corruption in WebAssembly. Reported by Man Yue Mo of GitHub Security Lab on 2024-03-27
[$3000][326607008] High CVE-2024-3834: Use after free in Downloads. Reported by ChaobinZhang on 2024-02-24
[$7000][41491379] Medium CVE-2024-3837: Use after free in QUIC. Reported by {rotiple, dch3ck} of CW Research Inc. on 2024-01-15
[$5000][328278717] Medium CVE-2024-3838: Inappropriate implementation in Autofill. Reported by Ardyan Vicky Ramadhan on 2024-03-06
[$5000][41491859] Medium CVE-2024-3839: Out of bounds read in Fonts. Reported by Ronald Crane (Zippenhop LLC) on 2024-01-16
[$3000][41493458] Medium CVE-2024-3840: Insufficient policy enforcement in Site Isolation. Reported by Ahmed ElMasry on 2024-01-22
[$1000][330376742] Medium CVE-2024-3841: Insufficient data validation in Browser Switcher. Reported by Oleg on 2024-03-19
[$TBD][41486690] Medium CVE-2024-3843: Insufficient data validation in Downloads. Reported by Azur on 2023-12-24
[$5000][40058873] Low CVE-2024-3844: Inappropriate implementation in Extensions. Reported by Alesandro Ortiz on 2022-02-23
[$3000][323583084] Low CVE-2024-3845: Inappropriate implementation in Network. Reported by Daniel Baulig on 2024-02-03
[$2000][40064754] Low CVE-2024-3846: Inappropriate implementation in Prompts. Reported by Ahmed ElMasry on 2023-05-23
[$1000][328690293] Low CVE-2024-3847: Insufficient policy enforcement in WebUI. Reported by Yan Zhu on 2024-03-08
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:
[334957582] 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.
Daniel Yip
Google Chrome
Source: Google Chrome Releases
Beta Channel Update for ChromeOS / ChromeOS Flex
Hello All,
The Beta channel has been updated to ChromeOS version 15823.30.0 with Chrome Browser version 124.0.6367.66 for most ChromeOS devices.
If you find new issues, please let us know one of the following ways:
- File a bug
- Visit our Chrome OS communities
- General: Chromebook Help Community
- Beta Specific: ChromeOS Beta Help Community
- Report an issue or send feedback on Chrome
Source: Google Chrome Releases
Launch the FigJam whiteboard app directly from Google Meet Series One Board 65 and Desk 27 devices
What’s changing
Who’s impacted
Why you’d use it
Additional details
Getting started
- Admins: When the Figma add-on is installed for your organization, your users will automatically be able to access the app from Board 65 or Desk 27 devices. Visit the Help Center to learn more about installing add-ons for your organization.
- End users: Visit the Help Center to learn more about using add-ons with Google Meet on Desk 27 and Board 65 devices.
Rollout pace
- Rapid Release and Scheduled Release domains: Available now.
Availability
- Available to all Google Workspace customers with Google Meet Board 65 and Desk 27 devices
Resources
Google Meet hardware Help: Use Add Ons with Google Meet on Desk 27 and Board 65
Google Workspace Admin Help: Install Marketplace apps for your organization
Google Help: Use Add-Ons with Google Meet on Desk 27 and Board 65
Google Workspace Updates Blog: Find and install third-party add-ons directly within Google Meet
Google Workspace Updates Blog: The next phase of digital whiteboarding for Google Workspace
Source: Google Workspace Updates
Dark mode now available in Google Drive web
What’s changing
Getting started
- Admins: There is no admin control for this feature.
- End users: To use Dark Mode, go to Drive > Settings > Appearance > Dark. Visit the Help Center to learn more about using Dark theme in Google Drive.
Rollout pace
- Rapid Release and Scheduled Release domains: Gradual rollout (up to 15 days for feature visibility) starting on April 16, 2024
Availability
- Available to all Google Workspace customers, Google Workspace Individual subscribers, and users with personal Google accounts