Chrome 155 Release Notes - Chrome Platform Status

https://chromestatus.com/release-notes/155

◆Supports displaying JPEG XL format images

Chrome 155 now supports decoding the 'JPEG XL' image format, allowing JPEG XL images to be displayed directly within web pages. The MIME type is 'image/jxl,' and Blink uses the 'jxl-rs' decoder, which is implemented in Rust with a focus on memory safety.

JPEG XL is an image format standardized as ISO/IEC 18181, and it supports progressive decoding, which displays images in stages, as well as wide color gamut, HDR, high bit depth, and animation.

The next-generation image file format 'JPEG XL' is reported to have 11% smaller file sizes and 13% higher image quality than the AVIF format - GIGAZINE

◆Web Crypto API now supports post-quantum cryptography algorithms.

Chrome 155 adds several new encryption algorithms to the 'Web Crypto API,' which allows browsers to access cryptographic processing, as follows:

ML-KEM 768, 1024

ML-DSA 44, 65, 87

・ChaCha20-Poly1305

X-Wing

ML-KEM is a post-quantum cryptography scheme used for key exchange, and ML-DSA is used for digital signatures. With the advancement of quantum computing in mind, web applications will also be able to handle post-quantum cryptography through browser-provided implementations.

◆ Easily customize list symbols with CSS's 'symbols()' function.

Chrome 155 introduced support for the CSS symbols() function. While it was previously possible to define custom counter styles using @counter-style, symbols() allows you to specify list symbols and sequential numbering on the fly without having to declare a named @counter-style beforehand.

For example, you can use any string as a list marker by writing it like this: 'list-style-type: symbols(cyclic '★' '☆');'. In addition to cyclic, it also supports counting methods such as numeric, alphabetic, symbolic, and fixed. symbols() can be used with 'list-style-type', 'list-style', 'counter()', and 'counters()'.

◆ 'margin-trim' removes the margins from the first and last elements within a container.

The CSS 'margin-trim' property is now supported. Using margin-trim, you can remove the outer margins of child elements placed at the beginning or end of a container. For example, when placing headings and paragraphs within an article card, it becomes easier to control the unintended spacing that can result from the top margin of the first element or the bottom margin of the last element using CSS.

It can be used with regular block containers and multi-column containers. However, its application to flex containers and grid containers, which was included in the previous specification draft, has been removed from the current specification.

◆ Use 'text-decoration-skip-spaces' to prevent underlining or other elements from appearing in blank spaces.

Chrome 155 also introduces the 'text-decoration-skip-spaces' property. This property controls whether text decorations such as underlines, overlines, and strikethroughs are drawn over whitespace. By skipping decorations only over whitespace, you can make links and other elements within text look more natural.

◆ Window maximization and minimization is now possible from the web application.

The Window Management API has been enhanced, allowing web applications with window management privileges to call maximize(), minimize(), and restore(). Additionally, setResizable() can be used to control whether users are allowed to resize windows.

Furthermore, the 'display-state' and 'resizable' media features have been added to allow CSS and scripts to determine the current window state and whether it is resizable.

Google explains that this will allow for a more natural implementation of features such as title bar manipulation, especially when running remote applications on web clients using VDI (Virtual Desktop Infrastructure).

◆Digital credentials can now be issued to wallets from the website.

Chrome 155 adds the ability to issue digital credentials to the 'Digital Credentials API.' This allows websites such as universities, government agencies, and banks to securely add digital credentials to users' mobile wallets.

Android uses the Credential Manager mechanism that supports IdentityCredential, while desktops utilize inter-device communication using the CTAP protocol, similar to the presentation function of Digital Credentials.

◆ Enables control over audio and video playback in hidden iframes.

Chrome 155 adds a new Permissions Policy called 'media-playback-while-not-visible'. By setting this Permissions Policy, the source of the embedded content can block playback of audio media when the embedded iframe is invisible to the user, such as when it has 'display: none', 'visibility: hidden', or has a width or height of 0. The restriction is lifted when the iframe is displayed again.

This prevents hidden embedded content from continuing to play audio in the background, and also reduces unnecessary media processing, leading to improved performance.

◆ JavaScript can now read text files as modules.

Chrome 155 introduced support for 'Import Text (Text Modules)' in JavaScript, which allows you to import text files as modules. Using syntax like 'import text from './sample.txt' with { type: 'text' }', you can directly import text data as a string.

◆Other updates

- 'srgb-linear' and 'display-p3-linear' have been added to the Predefined ColorSpaces available for use with Canvas.

- The 'atomic-vec2u-min-max' function has been added to WebGPU, making 64-bit atomic minimum and maximum value calculations for 'atomic<vec2u>' available in WGSL.

- The 'datagramsReadableType: 'bytes'' option has been added to WebTransport to handle received Datagrams as byte streams.

- The WebTransport Datagram transmission API has been extended to allow for the creation of independent WritableStreams and the specification of transmission priority.

WebTransport now includes 'reliability' and 'supportsReliableOnly' options to determine whether it supports only reliable communications or also allows unreliable communications such as Datagrams.

- A standardized 'WebTransportReceiveStream' has been added, making it possible to obtain the number of bytes received per stream and the number of bytes read by the application.

- For extensions using the 'chrome.debugger' API in enterprise-managed Chrome, administrator-defined host access restrictions and screenshot prohibition policies are now applied.

Additionally, Google Chrome 155 includes 247 security fixes.

Windows 11/10

Silent installation

 

https://www.mediafire.com/file/g0krl95uj8or4r3/Google+Chrome+155.0.8059.85+AIO+Silent+Install.7z/file

https://transfer.it/t/RxbC3GohEDzS

 

Windows 7/8

Silent installation

 

Google Chrome 109.0.5414.168 AIO windows 7 last version Install Silent 

https://www.mediafire.com/file/y480s6kyzu9k81l/Google+Chrome+109.0.5414.168+AIO+Install+Silent.7z/file

Edited 1 hour ago1 hr by T3rM1nat0Rr3

Google Chrome Changelog:

Google Chrome Changelog:

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

[TBD][409619251] Critical CVE-2025-3619: Heap buffer overflow in Codecs. Reported by Elias Hohl on 2025-04-09

[TBD][405292639] High CVE-2025-3620: Use after free in USB. Reported by @retsew0x01 on 2025-03-21

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.

PrudhviKumar Bommana Google Chrome

135.0.7049.115 new

Google Chrome 136.0.7103.93 update

Google Chrome 136.0.7103.114 update

137.0.7151.56 update

Google Chrome 137.0.7151.69 update

Google Chrome 137.0.7151.120 updates

Google Chrome 138.0.7204.50 update

https://developer.chrome.com/release-notes/138

  Hi, everyone! We've just released Chrome 138 (138.0.7204.157) 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: 138.0.7204.157/158, Linux: 138.0.7204.157) unless otherwise noted.

Krishna Govind

138.0.7204.169  Update

The Stable channel has been updated to 138.0.7204.183/.184 for Windows, Mac and 138.0.7204.183 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 includes4security fixes. Below, we highlight fixes that were contributed by external researchers. Please see theChrome Security Pagefor more information.

[$8000][426054987] High CVE-2025-8292: Use after free in Media Stream. Reported by Anonymous on 2025-06-19


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:

[434760450] Various fixes from internal audits, fuzzing and other initiatives

139.0.7258.139 update

139.0.7258.155 update

Google has released Chrome 140 to the stable channel for Windows,

The Stable channel has been updated to 140.0.7339.213/.214 for 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.

Srinivas Sista
Google Chrome

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

Chrome 141.0.7390.54 (Linux) 141.0.7390.54/55 Windows and 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 141.

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.

[$25000][442444724] High CVE-2025-11205: Heap buffer overflow in WebGPU. Reported by Atte Kettunen of OUSPG on 2025-09-02

[$4000][444755026] High CVE-2025-11206: Heap buffer overflow in Video. Reported by Elias Hohl on 2025-09-12

[$5000][428189824] Medium CVE-2025-11207: Side-channel information leakage in Storage. Reported by Alesandro Ortiz on 2025-06-27

[$3000][397878997] Medium CVE-2025-11208: Inappropriate implementation in Media. Reported by Kevin Joensen on 2025-02-20

[$3000][438226517] Medium CVE-2025-11209: Inappropriate implementation in Omnibox. Reported by Hafiizh on 2025-08-13

[$3000][440523110] Medium CVE-2025-11210: Side-channel information leakage in Tab. Reported by Umar Farooq  on 2025-08-22

[$3000][441917796] Medium CVE-2025-11211: Out of bounds read in Media. Reported by Kosir Jakob on 2025-08-29

[$2000][420734141] Medium CVE-2025-11212: Inappropriate implementation in Media. Reported by Ameen Basha M K on 2025-05-28

[$1000][443408317] Medium CVE-2025-11213: Inappropriate implementation in Omnibox. Reported by Hafiizh on 2025-09-06

[N/A][439758498] Medium CVE-2025-11215: Off by one error in V8. Reported by Google Big Sleep on 2025-08-19

[$1000][419721056] Low CVE-2025-11216: Inappropriate implementation in Storage. Reported by Farras Givari on 2025-05-23

[N/A][439772737] Low CVE-2025-11219: Use after free in V8. Reported by Google Big Sleep on 2025-08-19

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:

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

Srinivas Sista

Google Chrome

Google Chrome 141.0.7390.66 update

The Stable channel has been updated to 141.0.7390.76/.77 for Windows and Mac and 141.0.7390.76 for Linux, 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.