Quick answers
- Is CVE-2026-87595 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-87595 being exploited in the wild.
- How severe is CVE-2026-87595?
- Critical severity, with a CVSS score of 9.8, published 9 September 2026.
- Which products and versions are affected?
- Google Chrome prior to 153.0.8010.36.
- Is there a fix for CVE-2026-87595?
- A patch was published on 2026-09-08: Chrome 153.0.8010.36 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-87595 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-87595?
- 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
This vulnerability is a server-side request forgery (SSRF) flaw in the Mobile component of Google Chrome prior to version 153.0.8010.36. The vulnerability allows a remote attacker to bypass system access restrictions by crafting a malicious HTML page and leveraging social engineering to trick a user into visiting it. The attack requires user interaction (visiting the crafted page) but does not require prior authentication. While Chromium classified this as "Low" severity, the reported CVSS score of 9.8 suggests a critical impact potential. A patch was released in Chrome 153.0.8010.36 and later versions.
Affected products
- Google Chrome prior to 153.0.8010.36
Timeline
- 2026-09-09: disclosed
- 2026-09-08: patched: Chrome 153.0.8010.36 released