Quick answers
- Is CVE-2026-113343 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-113343 being exploited in the wild.
- How severe is CVE-2026-113343?
- Informational severity, published 20 October 2026.
- Which products and versions are affected?
- Google Chrome prior to 156.0.8078.47.
- Is there a fix for CVE-2026-113343?
- Yes: fixed in Chrome 156.0.8078.47 (Linux), 156.0.8078.48 (Windows/Mac). Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-113343 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-113343?
- 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.
How to fix
- Fixed in: Chrome 156.0.8078.47 (Linux), 156.0.8078.48 (Windows/Mac)
Technical details
Memory corruption in Chrome's Sandbox component allows remote code execution via a crafted HTML page. The vulnerability affects Chrome versions prior to 156.0.8078.47 and requires user interaction (visiting a malicious webpage) with a network attack vector. An attacker gains code execution within the sandbox security boundary; exploitation is not known to have occurred in the wild.
Affected products
- Google Chrome prior to 156.0.8078.47
Timeline
- 2026-10-20: disclosed