Google has released the new Chrome version 144 (Stable-channel) with the main goal of addressing a high-severity issue in the V8 JavaScript engine . The update comes as a reminder once again how critical it remains to update browsers in a timely manner , especially when it comes to vulnerabilities that can be exploited through simple web browsing.
When and how the update is available
Version 144.0.7559.96/.97 for Windows and macOS, as well as 144.0.7559.96 for Linux, began rolling out on January 21, 2026. As is Google's custom, the release is gradual, meaning it may take a few days or weeks to reach all users worldwide.
See also: UStrive: Security flaw exposed user personal data
Chrome 144: CVE-2026-1220 in the spotlight
This update fixes CVE-2026-1220 , a race condition flaw in the V8 JavaScript engine, which was reported by a security researcher on January 7, 2026. Race condition vulnerabilities occur when two or more processes attempt to access the same resources at the same time , creating unpredictable situations that can be exploited maliciously.
Why the V8 is so critical
V8 is the "heart" of Chrome, as it is responsible for executing JavaScript in almost every modern web page. A flaw at this level could allow memory corruption, cause browser instability , or, in the worst case, lead to arbitrary code execution. Given the massive use of Chrome, a successful exploit could affect millions of users.
High seriousness and limited details
Google has rated the vulnerability as high severity, reflecting the potential risk to end users. At the same time, the company follows a standard practice of limiting technical details until it is certain that the majority of users have already installed the update. This reduces the chances of direct exploitation by attackers.
See also: Vulnerabilities in Chainlit AI: Risk to servers
The role of automated security tools
The Chrome security team emphasizes that many of the bugs are detected thanks to advanced tools such as AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer, and AFL. These tools detect memory corruption and undefined behavior issues long before the code reaches the stable channel, significantly strengthening proactive defenses.
What users and businesses should do
Regular users can check the version they are running directly by going to Settings > About Chrome, where the browser automatically checks for updates. While Chrome usually updates itself in the background, manually checking offers extra peace of mind.
For organizations and IT administrators, prioritizing this update is critical. The existence of a high-severity vulnerability in the core JavaScript execution engine increases the risk of targeted attacks, especially in environments with increased internet exposure.
See also: Vulnerabilities in Anthropic MCP Git Server allow code execution
Transparency and collaboration with the community
Google continues to acknowledge the contribution of the security research community, noting that this collaboration is crucial in preventing serious incidents. The full changelog remains available in the Chromium repository, offering technical information for those who want to delve deeper.
Another message about safety
The release of Chrome 144 is a reminder that the browser is now a critical infrastructure. Keeping it up to date is not just about new features, but a key element of digital security. In a landscape of growing threats, regular maintenance remains the first line of defense.
