Skip to main content
VulnerabilityPublished

CVE-2026-106256: Google Chrome · Information Leak

Affects Google ChromeSource CVE Database V5

0
Compare

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

Data as of 20 Nov 2026, 17:34 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 17% 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:H/A:H

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

Google has released an official fix in Chrome version 155.0.8059.39. Users and administrators should update affected Chrome installations on Android to this version or later to remediate the vulnerability. No additional mitigation steps are indicated by the vendor advisory.

Description

CVE-2026-106256 is an information leak vulnerability in Google Chrome on Android versions prior to 155.0.8059.39. A remote attacker could exploit this flaw by tricking a user into visiting a crafted HTML page, potentially exposing sensitive password information. The vulnerability has a high severity rating with a CVSS score of 8.8. Google has released a stable channel update to address this issue.

References

Community reviews

Loading reviews…