Quick answers
- Is CVE-2026-15773 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-15773 being exploited in the wild.
- How severe is CVE-2026-15773?
- Critical severity, with a CVSS score of 9.6, published 14 July 2026.
- Which products and versions are affected?
- Google Chrome Prior to 150.0.7871.125.
- Is there a fix for CVE-2026-15773?
- A patch was published on 2026-07-14: Fixed in version 150.0.7871.125 for Windows Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-15773 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-15773?
- 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 Core component of Google Chrome for Windows. The flaw is triggered when the browser incorrectly manages memory during the processing of specially crafted HTML content. A remote, unauthenticated attacker can exploit this by enticing a user to visit a malicious webpage. Successful exploitation allows the attacker to break out of the Chromium sandbox and execute arbitrary code with the privileges of the user on the host Windows system. This issue was addressed in Chrome version 150.0.7871.125.
Affected products
- Google Chrome Prior to 150.0.7871.125
Timeline
- 2026-06-25: disclosed: Reported by xinchaotian of Microsoft
- 2026-07-14: patched: Fixed in version 150.0.7871.125 for Windows
- 2026-07-14: advisory