{"id":322828,"date":"2026-03-20T09:44:34","date_gmt":"2026-03-20T08:44:34","guid":{"rendered":"https:\/\/borncity.com\/blog\/?p=322828"},"modified":"2026-03-20T09:45:06","modified_gmt":"2026-03-20T08:45:06","slug":"google-chrome-146-0-7680-153-154-fixt-26-schwachstellen","status":"publish","type":"post","link":"https:\/\/borncity.com\/blog\/2026\/03\/20\/google-chrome-146-0-7680-153-154-fixt-26-schwachstellen\/","title":{"rendered":"Google Chrome 146.0.7680.153\/154 fixt 26 Schwachstellen"},"content":{"rendered":"<p><img decoding=\"async\" style=\"float: left; margin: 0px 10px 0px 0px; display: inline;\" src=\"https:\/\/borncity.com\/blog\/wp-content\/uploads\/2021\/06\/Chrome-01.jpg\" \/>Kurzer Hinweis f\u00fcr Nutzer des Google Chrome-Browsers. Google hat zum 18. M\u00e4rz 2026 eine neue Version 146.0.7680.153\/154 des Chrome ver\u00f6ffentlicht, die gleich 26 Schwachstellen im Browser beseitigt. Drei dieser Schwachstellen wurden als kritisch bewertet. Google will die neue Version stufenweise ausrollen.<\/p>\n<p><!--more--><\/p>\n<h2>Google Chrome (Stable) 146.0.7680.153\/154<\/h2>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/vg04.met.vgwort.de\/na\/ea43de3060184c1582ed717e830517ec\" alt=\"\" width=\"1\" height=\"1\" \/>Der <a href=\"https:\/\/chromereleases.googleblog.com\/2026\/03\/stable-channel-update-for-desktop_18.html\" target=\"_blank\" rel=\"noopener\">betreffende Eintrag<\/a> findet sich im <a href=\"https:\/\/chromereleases.googleblog.com\/\" target=\"_blank\" rel=\"noopener\">Google-Blog<\/a>. Der Stable-Channel wurde per Update f\u00fcr macOS und Windows auf die Version\u00a0146.0.7680.153\/154\u00a0aktualisiert. F\u00fcr Linux aktualisiert das Update den Browser auf die Version 146.0.7680.153 f. Laut Google wurden folgende Schwachstellen im Chrome geschlossen.<\/p>\n<ul>\n<li>[TBD][475877320] Critical CVE-2026-4439: Out of bounds memory access in WebGL. Reported by Goodluck on 2026-01-15<\/li>\n<li>[TBD][485935305] Critical CVE-2026-4440: Out of bounds read and write in WebGL. Reported by c6eed09fc8b174b0f3eebedcceb1e792 on 2026-02-20<\/li>\n<li>[TBD][489381399] Critical CVE-2026-4441: Use after free in Base. Reported by Google on 2026-03-03<\/li>\n<li>[TBD][484751092] High CVE-2026-4442: Heap buffer overflow in CSS. Reported by Syn4pse on 2026-02-16<\/li>\n<li>[TBD][485292589] High CVE-2026-4443: Heap buffer overflow in WebAudio. Reported by c6eed09fc8b174b0f3eebedcceb1e792 on 2026-02-18<\/li>\n<li>[TBD][486349161] High CVE-2026-4444: Stack buffer overflow in WebRTC. Reported by c6eed09fc8b174b0f3eebedcceb1e792 on 2026-02-21<\/li>\n<li>[TBD][486421953] High CVE-2026-4445: Use after free in WebRTC. Reported by c6eed09fc8b174b0f3eebedcceb1e792 on 2026-02-22<\/li>\n<li>[TBD][486421954] High CVE-2026-4446: Use after free in WebRTC. Reported by c6eed09fc8b174b0f3eebedcceb1e792 on 2026-02-22<\/li>\n<li>[TBD][486657483] High CVE-2026-4447: Inappropriate implementation in V8. Reported by Erge on 2026-02-23<\/li>\n<li>[TBD][486972661] High CVE-2026-4448: Heap buffer overflow in ANGLE. Reported by M. Fauzan Wijaya (Gh05t666nero) on 2026-02-23<\/li>\n<li>[TBD][487117772] High CVE-2026-4449: Use after free in Blink. Reported by Syn4pse on 2026-02-24<\/li>\n<li>[TBD][487746373] High CVE-2026-4450: Out of bounds write in V8. Reported by qymag1c on 2026-02-26<\/li>\n<li>[TBD][487768779] High CVE-2026-4451: Insufficient validation of untrusted input in Navigation. Reported by c6eed09fc8b174b0f3eebedcceb1e792 on 2026-02-26<\/li>\n<li>[TBD][487977696] High CVE-2026-4452: Integer overflow in ANGLE. Reported by cinzinga on 2026-02-26<\/li>\n<li>[TBD][488400770] High CVE-2026-4453: Integer overflow in Dawn. Reported by sweetchip on 2026-02-27<\/li>\n<li>[TBD][488585488] High CVE-2026-4454: Use after free in Network. Reported by heapracer (@heapracer) on 2026-03-01<\/li>\n<li>[TBD][488585504] High CVE-2026-4455: Heap buffer overflow in PDFium. Reported by c6eed09fc8b174b0f3eebedcceb1e792 on 2026-03-01<\/li>\n<li>[TBD][488617440] High CVE-2026-4456: Use after free in Digital Credentials API. Reported by sean wong on 2026-02-28<\/li>\n<li>[TBD][488803413] High CVE-2026-4457: Type Confusion in V8. Reported by Zhenpeng (Leo) Lin at depthfirst on 2026-03-01<\/li>\n<li>[TBD][489619753] High CVE-2026-4458: Use after free in Extensions. Reported by Shaheen Fazim on 2026-03-04<\/li>\n<li>[TBD][490246422] High CVE-2026-4459: Out of bounds read and write in WebAudio. Reported by Jihyeon Jeong (Compsec Lab, Seoul National University \/ Research Intern) on 2026-03-06<\/li>\n<li>[TBD][490254124] High CVE-2026-4460: Out of bounds read in Skia. Reported by c6eed09fc8b174b0f3eebedcceb1e792 on 2026-03-06<\/li>\n<li>[TBD][490558172] High CVE-2026-4461: Inappropriate implementation in V8. Reported by Google on 2026-03-07<\/li>\n<li>[TBD][491080830] High CVE-2026-4462: Out of bounds read in Blink. Reported by heapracer (@heapracer) on 2026-03-09<\/li>\n<li>[TBD][491358681] High CVE-2026-4463: Heap buffer overflow in WebRTC. Reported by c6eed09fc8b174b0f3eebedcceb1e792 on 2026-03-10<\/li>\n<li>[TBD][487208468] Medium CVE-2026-4464: Integer overflow in ANGLE. Reported by heesun on 2026-02-24<\/li>\n<\/ul>\n<p>Hinzu kommen verschiedene Korrekturen aus internen Audits, Fuzzing und anderen Initiativen. Sowohl der Google Chrome, als auch der Microsoft Edge-Browser, sollten sich, sofern betroffen, automatisch aktualisieren. Man kann auch versuchen, den Browser auch manuell (\u00fcber das Men\u00fc und den Befehl <em>\u00dcber Google Chrome<\/em>) zu aktualisieren. Die aktuelle Build des Chrome-Browsers f\u00fcr Windows l\u00e4sst sich auch <a href=\"https:\/\/www.google.com\/chrome\/\" target=\"_blank\" rel=\"noopener\">hier herunterladen<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Kurzer Hinweis f\u00fcr Nutzer des Google Chrome-Browsers. Google hat zum 18. M\u00e4rz 2026 eine neue Version 146.0.7680.153\/154 des Chrome ver\u00f6ffentlicht, die gleich 26 Schwachstellen im Browser beseitigt. Drei dieser Schwachstellen wurden als kritisch bewertet. Google will die neue Version stufenweise &hellip; <a href=\"https:\/\/borncity.com\/blog\/2026\/03\/20\/google-chrome-146-0-7680-153-154-fixt-26-schwachstellen\/\">Weiterlesen <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1356,426,7459,185],"tags":[406,4328,4315],"class_list":["post-322828","post","type-post","status-publish","format-standard","hentry","category-google-chrome-internet","category-sicherheit","category-software","category-update","tag-chrome","tag-sicherheit","tag-update"],"_links":{"self":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/322828","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/comments?post=322828"}],"version-history":[{"count":2,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/322828\/revisions"}],"predecessor-version":[{"id":322830,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/322828\/revisions\/322830"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/media?parent=322828"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/categories?post=322828"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/tags?post=322828"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}