Quick answers
- Is CVE-2026-106427 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-106427 being exploited in the wild.
- How severe is CVE-2026-106427?
- Informational severity, published 6 October 2026.
- Which products and versions are affected?
- Google Chrome prior to 155.0.8059.39 on iOS.
- Is there a fix for CVE-2026-106427?
- Yes: fixed in 155.0.8059.39. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-106427 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-106427?
- 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: 155.0.8059.39
Technical details
A confused deputy vulnerability in Chrome's Mobile component on iOS allows a remote attacker to bypass system access restrictions via a crafted HTML page, gaining access to privileged pages without proper authorization. This is a network-based attack requiring only the user to visit a malicious webpage. The vulnerability is fixed in Chrome version 155.0.8059.39 and later.
Affected products
- Google Chrome prior to 155.0.8059.39 on iOS
Timeline
- 2026-10-06: disclosed