Quick answers
- Is CVE-2026-110917 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-110917 being exploited in the wild.
- How severe is CVE-2026-110917?
- Medium severity, with a CVSS score of 4.3, published 15 October 2026.
- Which products and versions are affected?
- Google Chrome prior to 155.0.8059.84.
- Is there a fix for CVE-2026-110917?
- Yes: fixed in Chrome 155.0.8059.84 and later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-110917 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-110917?
- 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 155.0.8059.84 and later
Technical details
A memory corruption vulnerability exists in Chrome's SVG rendering component that allows remote code execution via a specially crafted HTML page. The vulnerability requires no user interaction beyond visiting a malicious webpage and can be triggered over the network. An attacker gains the ability to read arbitrary memory from the Chrome process.
Affected products
- Google Chrome prior to 155.0.8059.84
Timeline
- 2026-10-15: disclosed
- 2026-10-15: patched