Quick answers
- Is CVE-2026-126921 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-126921 being exploited in the wild.
- How severe is CVE-2026-126921?
- 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-126921?
- Yes: fixed in Chrome 157.0.8103.78. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-126921 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-126921?
- 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
Technical details
A use-after-free vulnerability exists in Chrome's Accessibility component (CVE-2026-126911) that can be triggered via a crafted HTML page sent over the network. The vulnerability allows remote code execution within the browser's sandbox without requiring user authentication or special privileges. The issue was patched in Chrome version 157.0.8103.78.
Affected products
- Google Chrome prior to 157.0.8103.78
Timeline
- 2026-11-11: disclosed
- 2026-11-11: patched