{"id":10024,"date":"2026-01-21T10:03:43","date_gmt":"2026-01-21T10:03:43","guid":{"rendered":"https:\/\/serisec.com\/index.php\/2026\/01\/21\/google-chrome-144-update-patches-high-severity-v8-vulnerability\/"},"modified":"2026-01-21T10:03:43","modified_gmt":"2026-01-21T10:03:43","slug":"google-chrome-144-update-patches-high-severity-v8-vulnerability","status":"publish","type":"post","link":"https:\/\/serisec.com\/index.php\/2026\/01\/21\/google-chrome-144-update-patches-high-severity-v8-vulnerability\/","title":{"rendered":"Google Chrome 144 Update Patches High-Severity V8 Vulnerability"},"content":{"rendered":"<p>    Google Chrome 144 Update Patches High-Severity V8 Vulnerability<br \/>\n \t<BR><br \/>\n<BR><\/BR><br \/>\n    <!-- no image --><br \/>\n \t<BR><br \/>\n<BR><\/BR><\/p>\n<div>\n<p>A new Stable-channel release of Chrome version 144 addresses a high-severity vulnerability in the <a href=\"https:\/\/cybersecuritynews.com\/chrome-v8-javascript-engine-vulnerability\/\" target=\"_blank\" rel=\"noreferrer noopener\">V8 JavaScript engine<\/a>.<\/p>\n<p>The update, version 144.0.7559.96\/.97 for Windows and Mac and 144.0.7559.96 for Linux, began rolling out on January 21, 2026, and will reach all users over the coming days and weeks.<\/p>\n<p>The security patch resolves CVE-2026-1220, a race condition in V8 reported by a security researcher on January 7, 2026.<\/p>\n<figure class=\"wp-block-table is-style-stripes\">\n<table class=\"has-fixed-layout\">\n<thead>\n<tr>\n<th class=\"has-text-align-left\" data-align=\"left\">CVE ID<\/th>\n<th class=\"has-text-align-left\" data-align=\"left\">Severity<\/th>\n<th class=\"has-text-align-left\" data-align=\"left\">Component<\/th>\n<th class=\"has-text-align-left\" data-align=\"left\">Description<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td class=\"has-text-align-left\" data-align=\"left\">CVE-2026-1220<\/td>\n<td class=\"has-text-align-left\" data-align=\"left\">High<\/td>\n<td class=\"has-text-align-left\" data-align=\"left\">V8<\/td>\n<td class=\"has-text-align-left\" data-align=\"left\">Race condition<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\n<h2 class=\"wp-block-heading\" id=\"h-critical-v8-vulnerability\"><strong>Critical V8 Vulnerability<\/strong><\/h2>\n<p>The flaw could be exploited through specially crafted web content, potentially resulting in <a href=\"https:\/\/cybersecuritynews.com\/firefox-high-severity-vulnerability\/\" target=\"_blank\" rel=\"noreferrer noopener\">memory corruption<\/a>, browser instability, or arbitrary code execution. Due to the browser\u2019s widespread use, successful exploitation could affect millions of users globally<\/p>\n<p>Race conditions occur when multiple processes access shared resources simultaneously, potentially allowing attackers to execute malicious code, crash the browser, or access sensitive information.<\/p>\n<p>V8 is Chrome\u2019s core JavaScript engine, making this vulnerability particularly concerning as it affects nearly all web-based functionality. Google has classified this as a high-severity issue, indicating significant risk to users.<\/p>\n<p>The company typically restricts access to detailed bug information until most users receive the update, preventing threat actors from exploiting the vulnerability before <a href=\"https:\/\/cybersecuritynews.com\/chrome-security-update-patch-v8-engine\/\" target=\"_blank\" rel=\"noreferrer noopener\">patches<\/a> are widely deployed.<\/p>\n<p>The<a href=\"https:\/\/cybersecuritynews.com\/chrome-144-released\/\" target=\"_blank\" rel=\"noreferrer noopener\"> Chrome 144<\/a> update follows Google\u2019s standard release cycle, with deployment gradually rolling out across platforms and regions.<\/p>\n<p>Users can verify their current version by navigating to Settings &gt; About Chrome, which automatically checks for updates and prompts installation if needed.<\/p>\n<p>Chrome\u2019s security team emphasizes that many vulnerabilities are detected using advanced automated tools, including AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, <a href=\"https:\/\/cybersecuritynews.com\/implementing-mitre-attck-in-soc\/\" target=\"_blank\" rel=\"noreferrer noopener\">Control Flow Integrity<\/a>, libFuzzer, and AFL.<\/p>\n<p>These tools help identify memory corruption issues, undefined behavior, and other security flaws before they reach the stable channel.<\/p>\n<p>Enterprise administrators managing Chrome deployments across organizations should prioritize this update given its high severity.<\/p>\n<p>The full changelog is available through the official Chromium source repository, providing technical details about all changes in this build.<\/p>\n<p>Google acknowledged the security research community\u2019s contributions, thanking researchers who work with the Chrome team during development cycles to prevent security bugs from reaching end users.<\/p>\n<p>Users are strongly encouraged to update their browsers immediately. Chrome typically updates automatically in the background, but manual verification ensures protection against this V8 <a href=\"https:\/\/cybersecuritynews.com\/?s=race+condition\" target=\"_blank\" rel=\"noreferrer noopener\">race condition<\/a>.<\/p>\n<p>The Chrome security page <a href=\"https:\/\/chromereleases.googleblog.com\/2026\/01\/stable-channel-update-for-desktop_20.html\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">provides<\/a> additional information about the browser\u2019s security architecture and ongoing initiatives to protect users from emerging threats.<\/p>\n<p>Google maintains its commitment to transparency while balancing responsible disclosure practices that protect users during the update rollout period.<\/p>\n<p class=\"has-text-align-center has-background\" style=\"background:linear-gradient(180deg,rgb(238,238,238) 94%,rgb(169,184,195) 100%)\"><strong>Follow us on <a href=\"https:\/\/news.google.com\/publications\/CAAqMggKIixDQklTR3dnTWFoY0tGV041WW1WeWMyVmpkWEpwZEhsdVpYZHpMbU52YlNnQVAB?hl=en-IN&amp;gl=IN&amp;ceid=IN:en\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">Google News<\/a>, <a href=\"https:\/\/www.linkedin.com\/company\/cybersecurity-news\/\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">LinkedIn<\/a>, and <a href=\"https:\/\/x.com\/cyber_press_org\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">X<\/a> for daily cybersecurity updates. <a href=\"https:\/\/cybersecuritynews.com\/contact-us\/\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">Contact us<\/a> to feature your stories.<\/strong><\/p>\n<p>The post <a href=\"https:\/\/cybersecuritynews.com\/chrome-144-patches-v8-vulnerability\/\">Google Chrome 144 Update Patches High-Severity V8 Vulnerability<\/a> appeared first on <a href=\"https:\/\/cybersecuritynews.com\/\">Cyber Security News<\/a>.<\/p>\n<\/div>\n<p> \t<BR><br \/>\n <BR><\/BR><br \/>\n    Abinaya<br \/>\n \t<BR><br \/>\n<BR><\/BR><br \/>\n<a href=\"https:\/\/cybersecuritynews.com\/chrome-144-patches-v8-vulnerability\/\">Go to cyber-security-news<\/a><br \/>\n \t<BR><br \/>\n <BR><\/BR><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Google Chrome 144 Update Patches High-Severity V8 Vulnerability A new Stable-channel release of Chrome version 144 addresses a high-severity vulnerability in the V8 JavaScript engine. The update, version 144.0.7559.96\/.97 for Windows and Mac and 144.0.7559.96 for Linux, began rolling out on January 21, 2026, and will reach all users over the coming days and weeks. [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[129,63,2178,648],"tags":[130],"class_list":["post-10024","post","type-post","status-publish","format-standard","hentry","category-cyber-security","category-cyber-security-news","category-security-updates","category-vulnerability-news","tag-cyber-security-news"],"_links":{"self":[{"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/posts\/10024"}],"collection":[{"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/comments?post=10024"}],"version-history":[{"count":0,"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/posts\/10024\/revisions"}],"wp:attachment":[{"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/media?parent=10024"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/categories?post=10024"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/tags?post=10024"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}