The latest version of Chrome 155 (v155.0.8059.84/.85) has fixed 10 security bugs. Some of them could be triggered by just visiting a malicious webpage. If successfully exploited, an attacker has the theoretical possibility of running their own code inside Chrome’s security sandbox.

We have attached a screenshot of the 10 security fixes below, and it includes the credits, as well as rewards.

Chrome security fixes.

Here are some terms that you need to know to understand the update:

  1. Use-after-free: Chrome tries to use a piece of memory that was already deleted/freed. Attackers can exploit this to crash the browser and execute their own code.
  2. Memory corruption: Something goes wrong with how Chrome handles memory.
  3. Prerender: A Chrome feature that pre-loads a webpage in the background before you click the link so that it can open instantly.
  4. DOM: The system that builds and manages the structure of a webpage.
  5. V8: Chrome’s JavaScript (JS) engine.
  6. SVG: Vector graphics.
  7. Workers: Background scripts that ensure your browser’s main/active page stays responsive.
  8. Improper input validation: Chrome doesn’t properly check some of the data that it receives, which attackers can exploit.

Now that you’re aware of these terms, you can understand the security content of this update better:

  1. Use-after-free error in Prerender: Chrome’s “background preload” feature had a problem where a malicious site could make Chrome use deleted memory while preparing a page, potentially allowing bad actors in.
  2. Memory corruption issues in DOM were fixed.
  3. Use-after-free issue in V8: A bug in the JS engine was fixed.
  4. Memory corruption issues in the browser’s core, V8 (JS engine), workers, and also SVG were fixed.
  5. Improper input validation issues on Chrome desktop have been addressed.
  6. User-after-free issue in Compositing: A bug in how Chrome draws the page on the screen.

Note: None of these are known to be actively exploited right now, but the critical Prerender bug is serious enough that we’d recommend updating immediately.

The update has already started rolling out to users at the time of writing. Immediately after firing up Chrome, I came across the v155.0.8059.85 update (on macOS). It should be available on Windows and Linux as well. You can view the entire changelog here.

Chrome latest version.

Meanwhile, Chrome 155 has also been released for Android. It mostly includes bug fixes and the same security improvements that Chrome desktop got.

In other Chrome news, the browser is finally getting a native “Copy Links” tool for tabs and groups. More on that here.

 
✦
PiunikaWeb’s Take

It’s a relief that these 10 bugs, especially the critical user-after-free bug, got caught and patched before others had a chance to exploit them. Many of these were fixed (some with Claude’s assistance); Google’s team and other researchers helped fix these unsettling security issues. Other Chromium browsers should pick up the same patches soon. One more thing: Chrome’s Git page for the raw commits wasn’t loading at the time of writing, so we couldn’t dig further into these changes or look for user-facing features. The changelog doesn’t mention any, and we didn’t find any after a short browse-through either.

We stand out from the tech-media crowd because we break news stories; we mainly bring you stuff that you won’t find anywhere in the mainstream tech media. Our stories have been picked up by some of the world’s most popular websites and media outlets—more info is available here.

Sudhanshu K
333 Posts

I have been a consumer technology enthusiast for over 5 years. Thanks to my experience in software beta testing and product reviews, I've understood and learnt a lot about what bugs and issues bother people, and I spend time trying to simplify their solutions. I cover smartphones, software, social media, apps, AI, and most consumer tech gadgets. Actively pursuing a Computer Science bachelor’s degree. I'm mostly active on Twitter/X (@TechWhirlUlt), drop a DM or tag me if you want to share info or connect!