Multiple Google Chrome Flaws Allow Attackers to Execute Arbitrary Code
Google has released Chrome version 141.0.7390.65/.66 for Windows and Mac, and version 141.0.7390.65 for Linux. This update addresses three significant security vulnerabilities related to memory handling errors that could potentially allow attackers to…
Google has released Chrome version 141.0.7390.65/.66 for Windows and Mac, and version 141.0.7390.65 for Linux. This update addresses three significant security vulnerabilities related to memory handling errors that could potentially allow attackers to execute arbitrary code within the browser.
These vulnerabilities were identified by external researchers through Google's vulnerability disclosure program. The rewards for these discoveries ranged from $3,000 to $5,000, depending on the complexity and severity of the issue.
CVE-2025-11458: A high-severity heap buffer overflow in Chrome Sync, discovered by "raven" at KunLun Lab, which can be exploited by crafting malicious synchronization data. This vulnerability was reported on September 5, 2025, and earned a $5,000 reward. CVE-2025-11460: A high-severity use-after-free flaw in the Storage component, disclosed by researcher Sombra on September 23, 2025. This flaw allows memory corruption via specially designed scripts or web pages. CVE-2025-11211: A medium-severity out-of-bounds read in WebCodecs, reported by Jakob Košir on August 29, 2025. It involves supplying malformed input to the media decoding API, potentially leading to data corruption. A $3,000 reward was issued for this discovery.
Users should update to Chrome 141.0.7390.65/.66 immediately. Automatic updates are enabled by default, but users can manually verify the update by navigating to the “About Google Chrome” section in their browser settings.
Google has released Chrome version 141.0.7390.65/.66 for Windows and Mac, and version 141.0.7390.65 for Linux.
Enterprises managing Chrome through group policies or management consoles should ensure the update is deployed across all endpoints promptly.
Web developers and administrators are advised to maintain strict Content Security Policy (CSP) headers and sanitize user-supplied data to limit the execution of untrusted scripts.
Security teams may consider deploying tools like AddressSanitizer and Control Flow Integrity to detect similar issues in early development stages. Google acknowledges its security partners, including AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer, and AFL, for their assistance in detection and prevention efforts.
Collaboration between researchers and vendors is essential to maintain the security of browsers and web applications.
Based on reporting by GBHackers.
