# CVE-2026-110917: Google Chrome memory corruption in SVG

Source: https://junglewise.ai/threats/cve-2026-110917-memory-corruption-in-svg-in-google-chrome-prior-to-155-0-8059-84  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-15. Updated: 2026-10-16  
License: CC BY 4.0 with a link back

CVE-2026-110917 · Severity: medium · CVSS 4.3 · Published 2026-10-15

Google Chrome, a web browser used by billions worldwide, contains a memory corruption vulnerability in its SVG (Scalable Vector Graphics) processing. An attacker can exploit this flaw by crafting a malicious HTML page that, when visited, allows them to read sensitive data from the browser's memory, potentially exposing passwords, authentication tokens, or personal information.

Technologies: [Google Chrome](https://junglewise.ai/threats/technologies/chrome). Vendors: [Google](https://junglewise.ai/threats/vendors/google).

## 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

## References

- [https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_01886704284.html](https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_01886704284.html)
- [https://issues.chromium.org/issues/569038297](https://issues.chromium.org/issues/569038297)

## Related threats

- [Google Chrome use after free in Prerender](https://junglewise.ai/threats/cve-2026-110922-use-after-free-in-prerender-in-google-chrome-prior-to-155-0-8059)
- [Google Chrome use-after-free in V8](https://junglewise.ai/threats/cve-2026-110921-use-after-free-in-v8-in-google-chrome-prior-to-155-0-8059-84)
- [Google Chrome memory corruption in V8](https://junglewise.ai/threats/cve-2026-110920-memory-corruption-in-v8-in-google-chrome-prior-to-155-0-8059-84)
- [Google Chrome use after free in V8](https://junglewise.ai/threats/cve-2026-110919-use-after-free-in-v8-in-google-chrome-prior-to-155-0-8059-84)
- [Google Chrome memory corruption in Core](https://junglewise.ai/threats/cve-2026-110918-memory-corruption-in-core-in-google-chrome-prior-to-155-0-8059)