Millions of Google Chrome users need to update their browser – do this to keep safe today

Millions of Google Chrome users are being warned about a zero day vulnerability that has been discovered in the world’s most popular browser. The high-severity flaw takes advantage of a weakness in the Chrome V8 JavaScript engine and Google has confirmed that bad actors have already utilised this to carry out attacks. Which makes it all the more pressing for the millions of Google Chrome users out there to take action to protect their browser and device right now.

After being informed of the flaw earlier this week Google worked at lighting-fast speed to release a fix within a day.

The necessary fix is being pushed out with Google Chrome version 100.0.4896.127 which is being rolled out to the stable channel for desktop in the coming days and weeks.

Google Chrome updates itself automatically, with the browser checking for updates and installing them when you close and relaunch the app.

However, if you’re the type of person that keeps Chrome open for an extended period of time you may be waiting some time for the necessary update to install.

Thankfully though, there’s a way you can kickstart Chrome into installing the latest update today.

To do this, simply head to the Chrome menu then choose Help and then About Google Chrome.

Doing this will let you see which version of Chrome you’re running and ensure the latest build is installed on your device.

Google revealed the latest update for Chrome, as well as details on the recently discovered vulnerability, in a blog post this week.

In it the Mountain View firm said: “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.

“Google is aware that an exploit for CVE-2022-1364 exists in the wild.”

The Chrome flaw was discovered by Twitter user @_clem1. Describing how quickly Google fixed this issue, Shane Huntley tweeted: “Another Chrome 0day (CVE-2022-1364) in the wild found by @_clem1. Reported to Chrome yesterday and updated release out now.

“Incredibly impressive how fast @googlechrome is getting at rolling out fixes”.