Quick answers
- Is CVE-2026-12440 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-12440 being exploited in the wild.
- How severe is CVE-2026-12440?
- Critical severity, with a CVSS score of 9.6, published 17 June 2026.
- Which products and versions are affected?
- Google Chrome Prior to 149.0.7827.155.
- Is there a fix for CVE-2026-12440?
- A patch was published on 2026-06-16: Stable channel update released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-12440 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-12440?
- 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.
Technical details
A use-after-free (UAF) vulnerability exists in the DigitalCredentials component of Google Chrome for Windows. The flaw is triggered when the browser incorrectly manages memory during the handling of digital credentials, allowing a remote attacker to execute arbitrary code. By enticing a user to visit a specially crafted HTML page, an attacker can exploit this memory corruption to escape the Chromium sandbox and execute commands with the privileges of the logged-in user. This vulnerability is addressed in Chrome version 149.0.7827.155.
Affected products
- Google Chrome Prior to 149.0.7827.155
Timeline
- 2026-06-03: other: Reported to Google
- 2026-06-16: patched: Stable channel update released
- 2026-06-17: disclosed: Public advisory published