Skip to main content
VulnerabilityPublished Updated

CVE-2026-106294: Google Chrome · Incomplete Cleanup

Affects Google ChromeSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.1 Critical : upgrade to 155.0.8059.39 as a priority.

Data as of 20 Nov 2026, 17:34 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 24% 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:N/S:U/C:H/I:N/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

A fix is available in Google Chrome version 155.0.8059.39. Users and administrators should update affected Chrome installations on Mac systems to this version or later to remediate the vulnerability. No additional mitigation steps are indicated by the vendor advisory.

Description

CVE-2026-106294 is a critical vulnerability in Google Chrome on Mac platforms prior to version 155.0.8059.39. It involves incomplete cleanup in the Chromoting component, which allows a remote attacker to bypass system access restrictions by sending crafted network traffic. The vulnerability has a high CVSS score of 9.1, indicating critical severity with high confidentiality impact and high availability impact. The issue affects versions before 155.0.8059.39 and has been addressed in that version.

References

Community reviews

Loading reviews…