Millions of internet users rely on Google Chrome every single day to work, shop, and connect with friends. Google has just released Chrome 144 to the stable channel for Windows, macOS, and Linux. This is a critical update that you should not ignore.
This new version is not just about shiny new features or cosmetic changes. It brings ten important security fixes that protect your computer from bad actors. Three of these fixes are rated as high severity. If you care about your digital privacy and safety, it is time to check your browser version right now.
The Arrival of Chrome 144
Google officially announced the promotion of Chrome 144 to the stable channel on January 14, 2026. The tech giant is rolling out this update gradually. This means some users might see it immediately while others might get it over the next few days or weeks.
The specific version numbers you need to look for are quite specific. For Linux users, the stable version is Chrome 144.0.7559.59. If you are using Windows or macOS, you should look for version 144.0.7559.59 or 144.0.7559.60.
Keeping track of these numbers ensures you are running the safest build available. This update cycle follows Google’s standard schedule to keep the web ecosystem secure. It is vital to stay updated because hackers often target outdated browsers.
Google Chrome browser logo on digital security shield background
Serious Security Flaws in V8 and Blink
The most alarming part of this update involves the core engines that make Chrome work. The security team at Google has patched three high-severity issues. Two of these major flaws were found in the V8 JavaScript engine.
V8 is the heart of Chrome. It processes the JavaScript code that powers modern interactive websites. When there is a bug in V8, it can allow attackers to do dangerous things on your computer.
One of the V8 issues is an “out-of-bounds memory access” flaw. In simple terms, this means the browser tries to read or write data in a memory location where it is not supposed to be. Hackers can sometimes use this trick to crash your browser or even steal information.
The second high-severity issue involves the Blink rendering engine. Blink is responsible for drawing the text and images you see on your screen. A flaw here could allow a malicious website to trick the browser into doing something unsafe.
Here is a quick breakdown of the high-severity threats:
- V8 Engine: Out-of-bounds memory access issue.
- V8 Engine: Inappropriate implementation flaw.
- Blink Engine: Rendering security vulnerability.
Other Risks You Should Know About
Chrome 144 does not stop at just the high-level threats. The Google team also resolved several medium and low-severity issues. These might sound less scary, but they are still important to fix.
One specific fix addresses a “use-after-free” bug in ANGLE. ANGLE is the graphics translation layer that Chrome uses to display 3D content and videos smoothly. A use-after-free bug occurs when a program tries to use a piece of memory after it has already been cleared. This can lead to crashes or unexpected behavior that hackers might exploit.
The update also fixes problems related to input validation in downloads. This ensures that the files you save are handled correctly by the browser.
There were also repairs made to incorrect security UI behavior. This is crucial because the browser needs to tell you the truth about whether a site is safe or not.
Summary of Medium and Low Severity Fixes:
| Component | Issue Type | Why It Matters |
|---|---|---|
| Downloads | Input Validation | Ensures safe file handling |
| Security UI | Incorrect Behavior | accurate safety warnings |
| Networking | Policy Enforcement | Prevents network bypasses |
| ANGLE | Use-After-Free | Fixes graphics memory errors |
Why Google Keeps Secrets
You might notice that Google has not released the full technical details of how these bugs work. This is a deliberate choice. Google restricts bug details until a majority of users have updated their browsers.
This strategy is known as responsible disclosure. If Google explained exactly how to break into Chrome version 143 right now, hackers would use that information to attack anyone who has not updated to version 144 yet.
Also, Chrome uses many third-party libraries. Sometimes a bug in Chrome is actually a bug in a shared piece of code used by other programs. Google keeps the details quiet to give those other projects time to fix the issue too.
How to Check for Updates
Chrome usually updates itself in the background when you close and reopen your browser. However, many of us leave our browsers open for days or weeks at a time. This prevents the update from installing.
You can manually trigger the update process in seconds.
Follow these simple steps:
- Look at the top right corner of your browser window.
- Click on the three vertical dots (the menu button).
- Hover your mouse over “Help” at the bottom of the list.
- Click on “About Google Chrome.”
A new tab will open. Chrome will automatically check for updates. If a new version is available, it will start downloading immediately. Once the download is done, you must click the “Relaunch” button to finish the process.
Your open tabs and windows will reopen automatically after the restart. It takes less than a minute, but it saves you from potential security headaches down the road.
Do not wait for the automatic update. With high-severity flaws in the V8 engine, it is better to be safe and update manually today.
Google has stated that more information regarding new features and larger changes in Chrome 144 will be shared separately. For now, the focus is strictly on getting these security patches to as many users as possible.
