Quick answers
- Is CVE-2026-121182 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-121182 being exploited in the wild.
- How severe is CVE-2026-121182?
- High severity, with a CVSS score of 8.8, published 3 November 2026.
- Which products and versions are affected?
- Google Chrome prior to 157.0.8103.38.
- Is there a fix for CVE-2026-121182?
- Yes: fixed in Chrome 157.0.8103.38 (Linux), 157.0.8103.39 (Windows/Mac). Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-121182 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-121182?
- 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.38 (Linux), 157.0.8103.39 (Windows/Mac)
Technical details
A use-after-free flaw in Chrome's DOM component allows remote code execution within the browser's sandbox when processing a malicious HTML page. The vulnerability requires no user authentication or special privileges, only that a user visits or is redirected to a malicious webpage. While sandboxed, successful exploitation could allow an attacker to read sensitive data, install malware, or pivot to other attack vectors.
Affected products
- Google Chrome prior to 157.0.8103.38
Timeline
- 2026-11-03: disclosed: Stable channel update published