Quick answers
- Is CVE-2026-5902 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-5902 being exploited in the wild.
- How severe is CVE-2026-5902?
- Critical severity, with a CVSS score of 9.8, published 8 April 2026.
- Which products and versions are affected?
- Google Chrome prior to 147.0.7727.55.
- Is there a fix for CVE-2026-5902?
- A patch was published on 2026-04-07: Stable channel update released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-5902 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-5902?
- Check whether you run Apple macOS, Google Chrome, Linux Kernel or one of the others listed 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 race condition vulnerability (CWE-362) exists in the Media component of Google Chrome for Android. The flaw is reachable if an attacker has already achieved code execution within the sandboxed renderer process. By enticing a user to visit a specially crafted HTML page, the attacker can exploit improper synchronization to corrupt media stream metadata. While Chromium classifies the severity as Low due to the prerequisite of a renderer compromise, CISA-ADP has assigned a Critical CVSS score of 9.8. The issue is resolved in version 147.0.7727.55.
Affected products
- Google Chrome prior to 147.0.7727.55
Timeline
- 2026-02-10: other: Vulnerability reported to Chromium
- 2026-04-07: patched: Stable channel update released
- 2026-04-08: disclosed: CVE published