CVE-2026-126909: Google Chrome use after free in Passwords

CVE-2026-126909 · Severity: info · Published 2026-11-11

A use-after-free vulnerability in Google Chrome's password management component allows attackers to execute arbitrary code outside the browser's security sandbox. An attacker can exploit this by crafting a malicious HTML page and using social engineering to trick users into visiting it, potentially leading to complete compromise of the user's system and data.

Technologies: Google Chrome. Vendors: Google.

Quick answers

Is CVE-2026-126909 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-126909 being exploited in the wild.
How severe is CVE-2026-126909?
Informational severity, published 11 November 2026.
Which products and versions are affected?
Google Chrome prior to 157.0.8103.78.
Is there a fix for CVE-2026-126909?
Yes: fixed in Chrome 157.0.8103.78 (Windows, Mac) and 157.0.8103.78 (Linux). Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-126909 attacked?
It is attacked over the network, in a web application.
Am I affected by CVE-2026-126909?
Check whether you run Google Chrome at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • Fixed in: Chrome 157.0.8103.78 (Windows, Mac) and 157.0.8103.78 (Linux)

Technical details

A use-after-free flaw in the Passwords component of Chromium allows an attacker to execute arbitrary code outside the sandbox boundary. The vulnerability requires social engineering (user visits a crafted HTML page) but results in code execution with elevated privileges. The vulnerability was fixed in Chrome version 157.0.8103.78 for Windows/Mac and Linux.

Affected products

  • Google Chrome prior to 157.0.8103.78

Timeline

  • 2026-10-11: disclosed: Vulnerability reported by JonathanBouman
  • 2026-11-11: patched: Fix released in Chrome 157.0.8103.78

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.