Skip to main content
VulnerabilityPublished Updated

CVE-2026-106396: Google Chrome · Improper Input Validation

Affects Google ChromeSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.3 High : upgrade to 155.0.8059.39 soon.

Data as of 20 Nov 2026, 17:50 UTC

CVSS 3.1 base score
7.3High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CISA-ADPCVSS 3.17.3
EPSS
0.2% chance of exploitation in 30 days – higher than 15% 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:L/UI:R/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
GoogleChromeAffected
  • >=155.0.8059.39 <155.0.8059.39
Fixed in
  • 155.0.8059.39

AI-suggested

Users should update Google Chrome on Android to version 155.0.8059.39 or later, where this vulnerability has been fixed. No additional mitigation steps are required as the issue is resolved by the official update.

Description

CVE-2026-106396 is a high-severity vulnerability in Google Chrome on Android prior to version 155.0.8059.39. It involves improper input validation in the Omnibox component, which could allow a remote attacker to bypass the web origin policy via a crafted HTML page combined with social engineering techniques. This flaw was fixed in Chrome version 155.0.8059.39.

References

Community reviews

Loading reviews…