https://chromereleases.googleblog.com/2024/06/stable-channel-update-for-desktop.html

Stable Channel Update for Desktop
Tuesday, June 11, 2024

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

Chrome 126.0.6478.54 (Linux)  126.0.6478.56/57( 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 126.

Chrome 126.0.6478.56/57( Windows, Mac) has been pushed to extended stable
channel as well

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

High CVE-2024-5830: Type Confusion in V8.
High CVE-2024-5831: Use after free in Dawn.
High CVE-2024-5832: Use after free in Dawn.
High CVE-2024-5833: Type Confusion in V8.
High CVE-2024-5834: Inappropriate implementation in Dawn.
High CVE-2024-5835: Heap buffer overflow in Tab Groups.
High CVE-2024-5836: Inappropriate Implementation in DevTools.
High CVE-2024-5837: Type Confusion in V8.
High CVE-2024-5838: Type Confusion in V8.
Medium CVE-2024-5839: Inappropriate Implementation in Memory Allocator.
Medium CVE-2024-5840: Policy Bypass in CORS.
Medium CVE-2024-5841: Use after free in V8.
Medium CVE-2024-5842: Use after free in Browser UI.
Medium CVE-2024-5843: Inappropriate implementation in Downloads.
Medium CVE-2024-5844: Heap buffer overflow in Tab Strip.
Medium CVE-2024-5845: Use after free in Audio.
Medium CVE-2024-5846: Use after free in PDFium.
Medium CVE-2024-5847: Use after free in PDFium.

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:

[346461939] 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.