CVE-2026-106242: Google Chrome · Information Leak
Affects Google ChromeSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium : upgrade to 155.0.8059.39 when convenient.
Data as of 20 Nov 2026, 17:34 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 155.0.8059.39
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 6 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.
What to do
Upgrade Google Chrome to 155.0.8059.39.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GoogleChrome | Affected
| Fixed in
|
AI-suggested
A stable channel update for Google Chrome has been released addressing this vulnerability in version 155.0.8059.39. Users should update to this version or later to remediate the issue. No additional mitigation steps are indicated by the vendor advisory.
Description
An information leak vulnerability exists in the Omnibox component of Google Chrome on Android versions prior to 155.0.8059.39. This flaw allows a remote attacker to leak sensitive information by leveraging social engineering and crafted network traffic. The vulnerability has a medium severity rating and does not require privileges but does require user interaction.