Skip to content
Connect AISign inSign up free
CVE-2026-1061979.6CriticalCWE-416

CVE-2026-106197: Google Chrome vulnerability

Google · Chrome

Fixed in Debian 12/13, openSUSE Leap 16.0 · Affected: Google Chrome · Exploitation: not established

At a glance

0.6%probability of exploitation in the next 30 days
47th percentile
050100

Higher than 47% of scored CVEs

9.6CriticalCVSS
LowCrit.

What it isNVD

Use after free in Browser in Google Chrome prior to 155.0.8059.39 allowed a remote attacker to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Critical)

Fix status by distribution

From each distribution’s security tracker. Distributions we did not check are not listed.

ExploitationNot established

Not in CISA KEV as of catalogue 2026.11.20 (20 Nov)

  1. Not establishedNothing in the sources we check

Not seen so far: in CISA KEV · exploited (reported) · scanning observed · proof of concept public.

Weakness and public checks

Public check
No public nuclei template
Weakness
Use After Free · Memory Corruption

Other CVEs in Chrome

Every published CVE for Google Chrome, by how far exploitation has gone. This one is among them.

As a list
Other CVEs in Chrome: each mark is one CVE.Drag to move · Ctrl + scroll to zoom · a mark opens that CVE

What changed

Debian status tracked since 6 Nov 2026. SUSE status tracked since 6 Nov 2026. Ubuntu status tracked since 20 Nov 2026.

  1. Ubuntu’s tracker lists Ubuntu 22.04 as not affected Ubuntu
  2. Ubuntu’s tracker lists Ubuntu 24.04 as not affected Ubuntu
  3. Ubuntu’s tracker lists Ubuntu 26.04 as not affected Ubuntu
  4. Ubuntu’s tracker lists Ubuntu stonking as not affected Ubuntu
  5. Seen in Debian’s tracker on 6 Nov: Debian 12 fixed in chromium 155.0.8059.39-1~deb12u1 (DLA-4833-1) Debian
  6. Seen in Debian’s tracker on 6 Nov: Debian 13 fixed in chromium 155.0.8059.39-1~deb13u1 (DSA-6553-1) Debian
  7. Seen in SUSE’s tracker on 6 Nov: openSUSE Leap 16.0 fixed SUSE

Coverage3 articles · 3 outlets

One row per outlet, in order of first report. First in our coverage: SecurityOnline, 7 Oct.

Full timeline
Quiet for 6 weekslast report 7 Oct3 articles3 outlets
7 Oct · SecurityOnline first31 Oct8 NovNow
  • Wed 7 Oct, 02:59 UTC. SecurityOnline, first report. Google Chrome 155 fixes 247 flaws, including four critical bugs.
  • Wed 7 Oct, 10:50 UTC. Malwarebytes, its first report on the story. Google Fixes Critical Chrome Flaws That Could Enable Remote Code Execution.
  • Wed 7 Oct, 11:29 UTC. SecurityWeek, its first report on the story. Chrome 155 patches 247 flaws, including four critical use after free bugs.
All coveragerunning total3SecurityOnl…1Malwarebytes1SecurityWeek17 Oct23 Oct8 NovNow
  • First report
  • Article
  • Running total
Show as table
3 articles about CVE-2026-106197 from 3 outlets
Published (UTC)OutletHeadline
7 Oct 02:59SecurityOnlineGoogle Chrome 155 fixes 247 flaws, including four critical bugs
7 Oct 10:50MalwarebytesGoogle Fixes Critical Chrome Flaws That Could Enable Remote Code Execution
7 Oct 11:29SecurityWeekChrome 155 patches 247 flaws, including four critical use after free bugs
  1. Google Chrome 155 fixes 247 flaws, including four critical bugs
    SecurityOnline · first in our coverage · mentions it in passing

New articles also arrive in the RSS feed.

References