Description

Google has released Chrome version 150.0.7871.186, delivering fixes for four high-severity security vulnerabilities affecting key browser components, including Codecs, WebMCP, Blink, and Input. At this time, the company has not observed any evidence that these flaws are being exploited in real-world attacks. As part of its standard disclosure process, Google has temporarily limited access to technical details and bug reports until the update reaches a broad user base. This approach helps reduce the likelihood of attackers developing exploits before most Chrome installations have been patched. The most severe issue, tracked as CVE-2026-16807, is an out-of-bounds write vulnerability in the Codecs component. Such memory handling flaws occur when data is written beyond the allocated buffer, potentially causing crashes or enabling arbitrary code execution under specific conditions. The update also addresses three use-after-free vulnerabilities: CVE-2026-16806 in WebMCP, CVE-2026-16805 in Blink, and CVE-2026-16804 in the Input component. These vulnerabilities arise when an application continues to reference memory after it has been released, creating opportunities for memory corruption or unintended program behavior. Since Blink is responsible for rendering web content and executing browser interactions, weaknesses in this component can have significant security implications. Similarly, vulnerabilities within media processing or input-handling functions could potentially be triggered through specially crafted web content, although Google has not yet disclosed the exact attack scenarios, proof-of-concept exploits, or exploitation requirements. According to Google's advisory, all four vulnerabilities were identified internally rather than by external researchers. The company credited its security engineering practices and automated testing technologies, including AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer, and AFL, for detecting these issues during development. Users can verify their installed version by opening Help > About Google Chrome, which also initiates an update check and prompts a browser restart if required. Enterprise administrators should prioritize deploying the latest release through managed update policies, particularly for systems processing sensitive information, while users are encouraged to relaunch Chrome after updating to ensure the security fixes are fully applied.