嗯，用户让我用中文帮他总结一篇文章，控制在100字以内，而且不需要用“文章内容总结”或者“这篇文章”这样的开头，直接写描述。好的，我先看看文章内容。 文章主要讲的是Google修复了Chrome浏览器中的三个漏洞，其中包括一个已经被利用的零日漏洞。这个漏洞编号是466192044，属于高危级别。Google没有透露太多技术细节，但提到这个漏洞是在ANGLE图形库中的Metal渲染器里，涉及到缓冲区大小计算错误，可能导致溢出和内存破坏。另外还有两个中危漏洞，分别涉及密码管理器和工具栏的问题。 此外，今年Google已经修复了七个其他被积极利用的零日漏洞，涉及V8引擎、ANGLE、Mojo等多个部分。Chrome的稳定版本已经更新到143.0.7499.109/.110，并将在未来几天或几周内推出更新。 现在我要把这些信息浓缩到100字以内。重点包括：Google修复了三个Chrome漏洞，其中一个是高危零日漏洞（编号466192044），涉及ANGLE图形库中的缓冲区溢出问题；另外两个中危漏洞；以及今年修复的其他七个零日漏洞；Chrome已更新到新版本。 可能需要省略一些细节，比如具体的漏洞编号和影响。确保语言简洁明了。 </think> Google修复了Chrome浏览器中的三个安全漏洞，包括一个已被利用的高危零日漏洞（编号466192044），该漏洞源于ANGLE图形库中的缓冲区溢出问题。此外还修复了两个中危漏洞，并在今年修复了其他七个被积极利用的零日漏洞。Chrome已更新至新版本以应对这些威胁。 2025-12-11 18:18:0 Author: securityaffairs.com(查看原文) 阅读量:6 收藏
Google fixed a new actively exploited Chrome zero-day
Pierluigi Paganini
December 11, 2025
Google addressed three vulnerabilities in the Chrome browser, including a high-severity bug already exploited in the wild.
Google released security updates to fix three vulnerabilities in the Chrome browser, including a high-severity flaw that threat actors are already exploiting in real-world attacks.
“Google is aware that an exploit for 466192044 exists in the wild,” reads the advisory published by Google.
Google tracked the high-severity vulnerability as Chromium issue 466192044, but the IT giant did not share technical details about the bug. A related GitHub commit, however, reveals the bug lies in the ANGLE graphics library, specifically its Metal renderer, where buffer sizes were incorrectly calculated using pixelsDepthPitch, derived from GL_UNPACK_IMAGE_HEIGHT. Because this value may be smaller than the actual image height, it can cause buffer overflows, leading to memory corruption, crashes, or potentially arbitrary code execution
Google also addressed the following Medium-severity vulnerabilities:
- [$2000][460599518]Medium CVE-2025-14372: Use after free in Password Manager. Reported by Weipeng Jiang (@Krace) of VRI on 2025-11-14
- [$2000][461532432]Medium CVE-2025-14373: Inappropriate implementation in Toolbar. Reported by Khalil Zhani on 2025-11-18
This year, Google addressed seven other zero-day vulnerabilities actively exploited in the wild:
- CVE-2025-6554 – The vulnerability is a type-confusing issue that resides in the V8 JavaScript and WebAssembly engine.
- CVE-2025-10585 – The vulnerability is a type confusion issue in the V8 JavaScript and WebAssembly engine.
- CVE-2025-6558 – The vulnerability is an insufficient validation of untrusted input in ANGLE and GPU in Google Chrome prior to 138.0.7204.157 that can allow a remote attacker to potentially perform a sandbox escape via a crafted HTML page.
- CVE-2025-5419 – The vulnerability is an out-of-bounds read and write in the V8 JavaScript engine in Google Chrome prior. An attacker can exploit the flaw to trigger a heap corruption via a crafted HTML page. The flaw is actively exploited in the wild.
- CVE-2025-4664 – The vulnerability is a Chrome browser vulnerability that could lead to full account takeover. Google is aware that an exploit for CVE-2025-5419 exists in the wild.
- CVE-2025-2783 – The vulnerability is an incorrect handle provided in unspecified circumstances in Mojo on Windows. Kaspersky researchers Boris Larin (@oct0xor) and Igor Kuznetsov (@2igosha) reported the vulnerability on March 20, 2025. Google released out-of-band fixes to address the high-severity security vulnerability in the Chrome browser for Windows. The flaw was actively exploited in attacks targeting organizations in Russia.
- CVE-2025-13223 – The vulnerability is a type confusion issue in the V8 JavaScript and WebAssembly engine.
Chrome Stable has been updated to 143.0.7499.109/.110 for Windows/macOS and 143.0.7499.109 for Linux, with rollout over the next days/weeks. Full changes are listed in the build log.
Follow me on Twitter: @securityaffairs and Facebook and Mastodon
(SecurityAffairs – hacking, Google)
如有侵权请联系:admin#unsafe.sh