Quick answers
- Is CVE-2026-93373 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-93373 being exploited in the wild.
- How severe is CVE-2026-93373?
- Critical severity, with a CVSS score of 9.6, published 17 September 2026.
- Which products and versions are affected?
- Google Chrome prior to 153.0.8010.52.
- Is there a fix for CVE-2026-93373?
- A patch was published on 2026-09-17: Fixed in Chrome 153.0.8010.52 and later Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-93373 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-93373?
- 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 vulnerability exists in the Chrome Extensions component, allowing an attacker to reference memory after it has been freed. The vulnerability can be triggered via a crafted Chrome extension and permits code execution outside the sandbox boundary. The attack vector requires the victim to install or accept a malicious extension, but once triggered, results in arbitrary code execution with full system privileges. This issue was patched in Chrome version 153.0.8010.52 and later. The vulnerability was reported to Google on 2026-08-26.
Affected products
- Google Chrome prior to 153.0.8010.52
Timeline
- 2026-09-17: disclosed
- 2026-09-17: patched: Fixed in Chrome 153.0.8010.52 and later