Stable Channel Update for ChromeOS / ChromeOS Flex

M-142, ChromeOS version 16433.41.0 (Browser version 142.0.7444.147) has rolled out to ChromeOS devices on the Stable channel. 

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.


Security Fixes and Rewards

ChromeOS Vulnerability Rewards Program Reported Bug Fixes:


N/A

Other 3rd Party Security Fixes Included:


N/A

Android Security fixes can be found here


Chrome Browser Security Fixes:


[$TBD] [452296415] High CVE-2025-12036 Inappropriate implementation in V8. Reported by Google Big Sleep on 2025-10-15

[$TBD] [452071845] Medium CVE-2025-12443 Out of bounds read in WebXR. Reported by Aisle Research on 2025-10-15

[$50000.0] [450618029] High CVE-2025-12429 Inappropriate implementation in V8. Reported by Aorui Zhang on 2025-10-10

[$TBD] [449760249] High CVE-2025-12433 Inappropriate implementation in V8. Reported by Google Big Sleep on 2025-10-07

[$50000.0] [447613211] High CVE-2025-12428 Type Confusion in V8. Reported by Man Yue Mo of GitHub Security Lab on 2025-09-26

[$2000.0] [446294487] Medium CVE-2025-12437 Use after free in PageInfo. Reported by Umar Farooq on 2025-09-20

[$TBD] [444049512] Medium CVE-2025-12441 Out of bounds read in V8. Reported by Google Big Sleep on 2025-09-10

[$10000.0] [442860743] High CVE-2025-12430 Object lifecycle issue in Media. Reported by round.about on 2025-09-04

[$TBD] [439522866] High CVE-2025-12432 Race in V8. Reported by Google Big Sleep on 2025-08-18

[$4000.0] [436887350] High CVE-2025-12431 Inappropriate implementation in Extensions. Reported by Alesandro Ortiz on 2025-08-06

[$1000.0] [433027577] Medium CVE-2025-12438 Use after free in Ozone. Reported by Wei Yuan of MoyunSec VLab on 2025-07-20

[$0.0] [430555440] Low CVE-2025-12440 Inappropriate implementation in Autofill. Reported by Khalil Zhani on 2025-07-09

[$1000.0] [428397712] Low CVE-2025-12445 Policy bypass in Extensions. Reported by Thomas Greiner on 2025-06-29

[$2000.0] [40054742] Medium CVE-2025-12436  Policy bypass in Extensions. Reported by Luan Herrera (@lbherrera_) on 2021-02-08

[$TBD] [454485895] High CVE-2025-12727 Inappropriate implementation in V8. Reported by 303f06e3 on 2025-10-23


Andy Wu

Google ChromeOS


Option for longer meeting notes with “take notes for me” in Google Meet

What’s happening

Meeting participants can now configure the length of their meeting notes when using the "take notes for me" feature in Google Meet. By selecting the "Longer" option from the "Notes Length" menu, you can generate notes that are roughly twice as long as the standard document to help capture all the important details. Turn on longer notes for technical discussions, complex project meetings, or any session where every detail is critical.

Caption: Longer notes can be enabled by selecting “Longer” in Notes Length settings. Alt text: An animation showing the process of selecting the “Longer” option in the Notes Length settings for the “Take notes for me” feature in Google Meet.

Caption: Longer notes can be enabled by selecting “Longer” in Notes Length settings.

Alt text: An animation showing the process of selecting the “Longer” option in the Notes Length settings for the “Take notes for me” feature in Google Meet.

Note: This feature is currently only available in English. 

Getting started

  • Admins: There is no admin control for this feature.
  • End users: This feature will be OFF by default and can be enabled by the user. Visit the Help Center to learn more.

Rollout pace

Availability

Available for Google Workspace:

  • Business Standard and Plus
  • Enterprise Standard and Plus
  • Google AI Pro for Education
  • Frontline Plus
Also available to:

  • Google One AI Premium 
  • Google AI Pro and Ultra
  • Gemini Business, Enterprise*
*As of January 15, 2025, we’re no longer offering the Gemini Business and Gemini Enterprise add-ons for sale. Please refer to this announcement for more details

Resources

Available in open beta: Migrate files from Dropbox to Google Drive

What’s changing

Beginning today, the new Data Migration Service can be used to migrate files and folders from Dropbox to Google Drive. This allows organizations to transition easily from Dropbox to Google Workspace, by copying over files, folders and associated permissions securely. 

You can start and complete a migration in a few simple steps:

  • Connect to your Dropbox business account from which you want to copy data.
  • Specify which users or team folders you want to copy from and which user’s MyDrive or Google shared drive should contain the copied data.
  • Specify users and groups whose permissions should be copied.
Example of a running Dropbox to Google Drive migration
Example of a running Dropbox to Google Drive migration

Additional details

  • You can migrate data from up to 100 Dropbox users or team folders at a time to MyDrive or Google shared drives respectively.
  • You can find comprehensive reporting on migration progress, including site and file counts (migrated/skipped). You can also export migration reports for error investigation and troubleshooting. 
  • Delta updates are available to migrate newly added or updated files.

Getting started

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
  • Education Fundamentals, Standard, Plus
  • Nonprofits

Resources


Improving secondary calendar management with dedicated owners

What’s happening

To improve data governance, we’re changing how secondary calendar ownership is defined in Google Calendar. A secondary calendar is any calendar that you create or a group calendar that is shared with you. Previously, secondary calendars could only be managed at the organization level. 

Going forward, each secondary calendar will have a single, dedicated owner. When a new secondary calendar is created, the creator becomes the calendar owner. For existing secondary calendars, an owner will be automatically assigned based on the calendar’s permissions. The calendar will inherit the organizational policies from its owner. This provides fine-grained control for admins to define policies for each calendar, such as data regions or assured controls.

Additionally, we’re introducing the ability to transfer secondary calendar ownership to another user in the same organization, through Google Calendar settings (for end users) or the Admin console (for admins). This is especially helpful when a calendar owner changes teams or leaves the organization, to ensure the calendar remains associated with the appropriate owner.

How the owner is shown in Calendar settings
How the owner is shown in Calendar settings

How the owner can be transferred from Calendar settings
How the owner can be transferred from Calendar settings
How the owner can be transferred in the Admin console
How the owner can be transferred in the Admin console

Additional details

The Google Calendar API has been updated to reflect these changes. Developers can retrieve the secondary calendar owner using the API for Calendars and CalendarList. In addition, we’ve added updates to ensure only the secondary calendar owner can delete the calendar, and that their access level cannot be downgraded as long as they are the owner.

Please refer to the API release notes for additional information.

Getting started

  • Admins: This feature will be ON by default and cannot be disabled. To help manage this transition, admins can now transfer the ownership of secondary calendars from one user to another directly in the Admin console.
  • End users: This feature will be ON by default and cannot be disabled. For existing secondary calendars, an owner will be automatically assigned based on the calendar’s permissions. End users who own a secondary calendar can transfer ownership to another user.

Rollout pace

Availability

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

New AI-powered audio overviews for PDFs in Google Drive

What’s happening

We’re introducing AI-powered audio overviews for PDFs in Google Drive.

This new Gemini for Google Workspace feature allows your users to instantly convert long, text-heavy PDFs—such as industry reports, contracts, or lengthy meeting transcripts—into a conversational, podcast-style audio summary. With just one click, a new audio file is saved directly to their Drive. This feature is powered by the same underlying technology as NotebookLM’s popular Audio Overview feature.


Add GIF

In today's fast-paced environment, dedicating time to read long documents can be a significant challenge. Audio overviews solve this by allowing users to absorb critical information while they are multitasking. Users can listen to the summaries from anywhere they can access their Drive files, whether they’re commuting, working out, or doing chores.

This feature can help your users:


  • Boost efficiency by allowing users to quickly grasp the main points of a long document in a two- to 10-minute audio summary,
  • Improve accessibility by providing an alternative format for consuming content, and
  • Enhance preparation by making it easier to quickly review materials before meetings or client presentations.
Once the audio overview is generated on a desktop, the user receives an email notification that the file is ready. The audio file is automatically saved to a new "Audio overviews" folder in their Drive, which they can then access from any mobile or desktop device.

Please note: At launch, this feature supports English-language PDFs only.

Getting started

Rollout pace

Availability

Available for Google Workspace

  • Business Standard and Plus 
  • Enterprise Standard and Plus 
Also available to

  • Google One AI Pro and AI Ultra
  • Google AI Ultra for Business
  • Google AI Pro for Education 

Resources

How JAX makes high-performance economics accessible

How JAX makes high-performance economics accessible

JAX is widely recognized for its power in training large-scale AI models, but its core design as a system for composable function transformations unlocks its potential in a much broader scientific landscape. We're seeing adoption for applications as disparate as AI-driven protein engineering to solving high-order Partial Differential Equations (PDEs). Today, we're excited to highlight another frontier where JAX is making a significant impact: enabling economists to model complex, real-world scenarios that shape national policy—computational economics.
I recently spoke with economist John Stachurski, a co-founder of QuantEcon and an early advocate for open-source scientific computing. His story of collaborating with the Central Bank of Chile demonstrates how JAX makes achieving performance easy and accessible. John's journey shows how JAX's intuitive design and abstractions allow domain experts to solve scientific problems without needing to become parallel programming specialists. John shares the story in his own words.


A Tale of Two Implementations: The Central Bank of Chile's Challenge
Due to my work with QuantEcon, I was contacted by the Central Bank of Chile (CBC), which was facing a computational bottleneck with one of their core models. The bank's work is high-stakes; their role is to set monetary policy and act as the lender of last resort during financial crises. Such crises are inherently non-linear in nature, involving self-reinforcing cycles and feedback loops that make them challenging to model and assess.
To better prepare themselves for such crises, the CBC began working on a model originally developed by Jarvier Bianchi, in which an economic shock worsens the balance sheets of domestic economic agents, reducing collateral and tightening credit constraints. This leads to further deterioration in balance sheets, which again tightens credit constraints, and so on. The result is a downward spiral. The ramifications can be large in a country such as Chile, where economic and political instability are historically linked.

The Problem:

The task of implementing this model was led by talented CBC economist Carlos Rondon. Carlos wrote the first version using a well-known proprietary package for mathematical modeling that has been used extensively by economists over the past few decades. The completed model took 12 hours to run -- that is, to generate prices and quantities implied by a fixed set of parameters -- on a $10,000 mainframe with 356 CPUs and a terabyte of RAM. A 12 hour run-time made it almost impossible to calibrate the model and run useful scenarios. A better solution had to be found.

Carlos and I agreed that the problem was rooted in the underlying software package. The issue was that, to avoid using slow loops, all operations needed to be vectorized, so that they could be passed to precompiled binaries generated from Fortran libraries such as LAPACK. However, as users of these traditional vectorization-based environments will know, it is often necessary to generate many intermediate arrays in order to obtain a given output array. When these arrays are high-dimensional, this process is slow and extremely memory intensive. Moreover, while some manual parallelization is possible, truly efficient parallelization is difficult to achieve.

The JAX Solution:

I flew to Santiago and we began a complete rewrite in JAX. Working side-by-side, we soon found that JAX was exactly the right tool for our task. In only two days we were able to reimplement the model and — running on a consumer-grade GPU — we observed a dramatic improvement in wall-clock time . The algorithm was unchanged, but even a cheap GPU outperformed the industrial server by a factor of a thousand. Now the model was fully operational: fast, clean, and ready for calibration.
There were several factors behind the project's success. First, JAX's elegant functional style allowed us to express the economic model's logic in a way that closely mirrored the underlying mathematics. Second, we fully exploited JAX's vmap by layering it to represent nested for loops. This allowed us to work with functions that operate on scalar values (think of a function that performs the calculations on the inside of a nested for loop), rather than attempting to operate directly on high dimensional arrays — a process that is inherently error-prone and difficult to visualize.

Third, JAX automates parallelization and does it extremely efficiently. We both had experience with manual parallelization prior to using JAX. I even fancied I was good at this task. But, at the end of the day, the majority of our expertise is in economics and mathematics, not computer science. Once we handed over parallelization to JAX's compiler OpenXLA we saw a massive speed up. Of course, the fact that XLA generates specialised GPU kernels on the fly was a key part of our success.
I have to stress how much I enjoyed completing this project with JAX. First, we could write code on a laptop and then run exactly the same code on any GPU, without changing a single line. Second, for scientific computing, the pairing of an interpreted language like Python with a powerful JIT compiler provides the ideal combination of interactivity and speed. To my mind, everything about the JAX framework and compilers is just right. A functional programming style makes perfect sense in a world where functions are individually JIT-compiled. Once we adopt this paradigm, everything becomes cleaner. Throw in automatic differentiation and NumPy API compatibility and you have a close-to-perfect environment for writing high performance code for economic modeling.


Unlocking the Next Generation of Economic Models

John's story captures the essence of JAX's power. By making high performance accessible to researchers, JAX is not just accelerating existing workloads; it's democratizing access to performance and enabling entirely new avenues of research.
As economists build models that incorporate more realistic heterogeneity—such as varying wealth levels, firm sizes, ages, and education—JAX enables them to take full advantage of modern accelerators like GPUs and Google TPUs. JAX's strengths in both scientific computing and deep learning make it the ideal foundation to bridge this gap.

Explore the JAX Scientific Computing Ecosystem

Stories like John's highlight a growing trend: JAX is much more than a framework for building the largest machine learning models on the planet. It is a powerful, general-purpose framework for array-based computing across all sciences which, together with accelerators such as Google TPUs and GPUs, is empowering a new generation of scientific discovery. The JAX team at Google is committed to supporting and growing this vibrant ecosystem, and that starts with hearing directly from you.

  • Share your story: Are you using JAX to tackle a challenging scientific problem? We would love to learn how JAX is accelerating your research.
  • Help guide our roadmap: Are there new features or capabilities that would unlock your next breakthrough? Your feature requests are essential for guiding the evolution of JAX.

Please reach out to the team via GitHub to share your work or discuss what you need from JAX. You can also find documentation, examples, news, events, and more at jaxstack.ai and jax.dev.

Sincere thanks to John Stachurski for sharing his insightful journey with us. We're excited to see how he and other researchers continue to leverage JAX to solve the world's most complex scientific problems.

Leverage the power of Gemini models to apply data classification labels in Google Drive – beta applications now open

What’s changing

Earlier this year, we announced a series of changes to AI classification for Google Drive, including a revamped user interface, an on-demand model training process, and support for multiple custom-trained models. Today, we’re excited to share the next step in the product’s evolution: Gemini-based models for data classification, now available in closed beta.  

This feature leverages Gemini models to apply data classification labels to files in Google Drive. To date, AI classification requires admins to identify and manually label training files for the AI model to learn the types of data associated with each data classification level. With this new capability, Gemini models offers admins another method to set up AI classification by eliminating the need for manual model training, replacing the process with administrator-defined instructions or prompts.

Gemini models interpret prompts, evaluate files, and apply appropriate data classification labels based on the provided instructions. For files labeled by Gemini, editors and owners on those files with the appropriate label permissions will have the opportunity to review and accept or modify the automatically applied label. 

Administrators maintain full control.

Administrators maintain full control. They select the label, provide instructions via a prompt, and scope the audience whose files are being evaluated. Audit logs capture when files are labeled or any user acceptance or modification of a Gemini-applied label occurs.  

Who’s impacted

Admins 

Why it matters

Data classification is a critical activity for organizations that are conscious about data protection, compliance, and reporting. However, data classification can also be challenging to put into practice, particularly when it comes to accurately classifying files at scale.  Using AI for data classification aims to address this problem by using a model’s ability to reason to achieve a high degree of data classification accuracy, at scale. 

Rollout pace

  • Closed Beta - customers must be manually enrolled to begin testing.

Getting started

  • Admins:  For customers interested in testing, we kindly ask that you share your interest by filling out this form
    • Please note – during this phase of product validation, enrollment will be limited. Our intent is to gradually onboard customers leading up to an Open Beta. 
    • Ideal closed-beta participants will be organizations with existing data classification programs, who have the capacity to actively test the models and are willing to engage with the Workspace product team to provide direct feedback on their experience. 
    • If you are selected for the Closed Beta, you will receive an email detailing specific onboarding instructions. 
  • End users: There is no end user setting for this feature.

Availability

Available to Google Workspace:

  • Enterprise Plus 

Resources