Quick answers
- Is CVE-2026-87897 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-87897 being exploited in the wild.
- How severe is CVE-2026-87897?
- Medium severity, with a CVSS score of 4.6, published 27 October 2026.
- Which products and versions are affected?
- Google Chrome.
- Is there a fix for CVE-2026-87897?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-87897 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-87897?
- Check whether you run Google Chrome. 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 SSRF vulnerability permits an attacker to make requests to internal Chrome Devtools Protocol APIs, which expose JWT authentication tokens. The attacker can trigger token leakage by monitoring when a victim initiates a recording session. Once a JWT token is captured, the attacker can impersonate the victim and access their Whiteboard data with full read/write permissions.
Affected products
- Google Chrome
Timeline
- 2026-10-27: disclosed