CVE-2026-106328: Google Chrome · Incorrect Authorization
Affects Google ChromeSource CVE Database V5
Not known to be exploited · CVSS 5.9 Medium : upgrade to 155.0.8059.39 when convenient.
Data as of 20 Nov 2026, 17:34 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% 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:H/PR:N/UI:N/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
Google has released a stable channel update for Chrome on Android that fixes this vulnerability. Users and administrators should update to version 155.0.8059.39 or later to remediate this issue. Since the vendor has provided an official fix, applying this update is the recommended mitigation.
Description
CVE-2026-106328 is a medium severity vulnerability in Google Chrome on Android prior to version 155.0.8059.39. It involves incorrect authorization in PDF handling that could allow a local attacker, leveraging social engineering and a co-installed app, to access sensitive information. Google has released a stable channel update that addresses this issue. There are no known exploits in the wild.