{"id":2574,"date":"2026-10-10T08:36:15","date_gmt":"2026-10-10T08:36:15","guid":{"rendered":"https:\/\/newsraise.com\/in\/2026\/10\/10\/google-chrome-155-update-fixes-247-vulnerabilities\/"},"modified":"2026-10-10T08:36:15","modified_gmt":"2026-10-10T08:36:15","slug":"google-chrome-155-update-fixes-247-vulnerabilities","status":"publish","type":"post","link":"https:\/\/newsraise.com\/in\/2026\/10\/10\/google-chrome-155-update-fixes-247-vulnerabilities\/","title":{"rendered":"Google Rolls Out Chrome 155 Update Fixing 247 Vulnerabilities, Including Four Critical Bugs"},"content":{"rendered":"\n<!-- Quick Adsense WordPress Plugin: http:\/\/quickadsense.com\/ -->\n<div class=\"9fece8afa224fd09e54b043d0febfb58\" data-index=\"1\" style=\"float: none; margin:10px 0 10px 0; text-align:center;\">\n<script async src=\"https:\/\/pagead2.googlesyndication.com\/pagead\/js\/adsbygoogle.js\"><\/script>\r\n<!-- NR ATF -->\r\n<ins class=\"adsbygoogle\"\r\n     style=\"display:block\"\r\n     data-ad-client=\"ca-pub-8898941184964366\"\r\n     data-ad-slot=\"4839033563\"\r\n     data-ad-format=\"auto\"\r\n     data-full-width-responsive=\"true\"><\/ins>\r\n<script>\r\n     (adsbygoogle = window.adsbygoogle || []).push({});\r\n<\/script>\n<\/div>\n<p>Google announced the availability of Chrome version 155, a security\u2011focused release that addresses a total of 247 vulnerabilities. Among the fixes are four flaws classified as Critical, all of which have been resolved before any known exploitation. The update is being distributed to users of Windows, macOS and Linux, with rollout expected to continue over the next several days and weeks.<\/p>\n<h2>Critical Use\u2011After\u2011Free Bugs and Their Scope<\/h2>\n<p>The four Critical vulnerabilities share a common technical characteristic: they are all &#8220;use\u2011after\u2011free&#8221; bugs. In a use\u2011after\u2011free scenario, a program continues to reference memory that has already been released, creating an opportunity for crashes, memory corruption, or the execution of malicious code. Google\u2019s release notes identify the specific components affected by each bug: a Chromecast\u2011related issue (CVE\u20112026\u2011106382), a generic browser flaw (CVE\u20112026\u2011106197), a navigation\u2011related problem (CVE\u20112026\u2011106358) and a tracking\u2011module defect (CVE\u20112026\u2011106347). The first of these was discovered internally by Google, while the remaining three were reported by Xinyang Ge, a technical staff member at Anthropic, who also uncovered more than ten additional High\u2011severity flaws.<\/p>\n<p>Beyond the Critical category, Chrome 155 resolves 53 High\u2011severity, 122 Medium\u2011severity and 68 Low\u2011severity vulnerabilities. The comprehensive nature of the patch set reflects Google\u2019s ongoing effort to harden the browser against a broad spectrum of attack vectors, ranging from privilege escalation to information leakage.<\/p>\n<h2>Recent Threat Landscape and Historical Context<\/h2>\n<p>Google has not indicated that any of the four Critical bugs have been weaponised in the wild, but the broader threat environment for Chrome remains active. Earlier in the year, the company addressed a critical vulnerability in Pixel smartphones (CVE\u20112026\u201158704) that enabled remote, zero\u2011click access to devices. In September, Google also patched CVE\u20112026\u201185046, a flaw in the V8 JavaScript engine that was already being exploited, marking the sixth known Chrome zero\u2011day used by attackers that year. Subsequent reports suggested a seventh exploit surfaced shortly thereafter.<\/p>\n<p>A September campaign highlighted the practical risk of such flaws. Four espionage groups employed the BlueMoon exploit kit to chain together Chrome and Windows zero\u2011day vulnerabilities, targeting organisations in the United States and Southeast Asia. While the current Chrome 155 release does not appear to be linked to active exploitation, the historical pattern underscores the importance of timely patch deployment.<\/p>\n<p>Chrome 155 follows a significant update released only weeks earlier. Chrome 154 addressed 108 vulnerabilities, including 11 classified as Critical. By contrast, the new release more than doubles the total number of fixes, though a higher count does not automatically translate to a more dangerous release. The real risk associated with each flaw depends on factors such as exploit complexity, user exposure and whether threat actors are actively leveraging the vulnerability.<\/p>\n<p>For end users and enterprise administrators, the update process remains largely automated. Chrome typically checks for and applies updates in the background, but a browser restart is required for the new version to become active. In managed environments, IT teams can control rollout timing through standard update policies. The version numbers to look for are 155.0.8059.39 or 155.0.8059.40 on Windows and macOS, and 155.0.8059.39 on Linux. Users can verify their current version by opening Chrome, selecting the menu, and navigating to Help\u202f\u2192\u202fAbout Google Chrome, where the browser will initiate any pending update and prompt for a restart if needed.<\/p>\n<p>Security professionals are advised to confirm that the Chrome 155 patches have reached all corporate devices, especially given the large volume of fixes and the ongoing prevalence of Chrome\u2011targeted attacks. While the sheer number of addressed flaws signals a robust response, each vulnerability\u2019s severity rating provides guidance on prioritisation. Critical use\u2011after\u2011free bugs, for instance, demand immediate attention because of their potential to enable arbitrary code execution if left unpatched.<\/p>\n<p>Overall, Chrome 155 represents Google\u2019s most extensive security effort for the browser to date in 2026, aiming to close gaps across a wide range of components and to stay ahead of a threat landscape that has repeatedly demonstrated interest in Chrome\u2019s code base. Users who keep their browsers up to date will benefit from the strengthened defenses, while organisations should continue to monitor patch compliance as part of broader cybersecurity hygiene.<\/p>\n\n<div style=\"font-size: 0px; height: 0px; line-height: 0px; margin: 0; padding: 0; clear: both;\"><\/div>","protected":false},"excerpt":{"rendered":"<p>Google has released Chrome 155, patching 247 security flaws across Windows, macOS and Linux, with four critical use\u2011after\u2011free bugs addressed.<\/p>\n","protected":false},"author":3,"featured_media":2575,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[299],"tags":[1960,2825,1958,2542,2824],"class_list":["post-2574","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news","tag-browser-security","tag-critical-bugs","tag-google-chrome","tag-security-update","tag-software-vulnerabilities","entry"],"_links":{"self":[{"href":"https:\/\/newsraise.com\/in\/wp-json\/wp\/v2\/posts\/2574","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/newsraise.com\/in\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/newsraise.com\/in\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/newsraise.com\/in\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/newsraise.com\/in\/wp-json\/wp\/v2\/comments?post=2574"}],"version-history":[{"count":0,"href":"https:\/\/newsraise.com\/in\/wp-json\/wp\/v2\/posts\/2574\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/newsraise.com\/in\/wp-json\/wp\/v2\/media\/2575"}],"wp:attachment":[{"href":"https:\/\/newsraise.com\/in\/wp-json\/wp\/v2\/media?parent=2574"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/newsraise.com\/in\/wp-json\/wp\/v2\/categories?post=2574"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/newsraise.com\/in\/wp-json\/wp\/v2\/tags?post=2574"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}