How do I check whether I am affected by CVE-2026-113155?

Open chrome://version and compare the version with 156.0.8078.47. On managed fleets, query the Chrome version from your device management console.

What is the fix for CVE-2026-113155?

Update Google Chrome to 156.0.8078.47 or later and restart the browser.

Who is not affected by CVE-2026-113155?

Not affected if: already-on-156.0.8078.47-or-later.

Live › vulnerability › CVE-2026-113155

Go to dashboard

high8.8Vendor

Chrome: use-after-free in Glic lets a crafted page run code

A use-after-free bug in the Glic component of Google Chrome before 156.0.8078.47 lets a remote attacker run code inside the browser sandbox by serving a crafted HTML page. Exploitation needs a victim to load the attacker's page, and the sandbox limits what the code can reach on its own.

Summary written from the sources below. Check the originals before acting.

CVSS 3.x

8.8

high

scored by 134c704f-9b21-4f2e-91b3-4a467353bcc0

known so far4 of 6

missing: primary source, exploitation

First public: Oct 20, 2026 UTC
Last modified: Oct 22, 2026
Status: open
Known exploitation: None reported
Public exploit: None on GitHub
EPSS: not scored

First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.

Why it is high, and not just CVSS

Likelihood → · Impact ↓

critical

high

medium

high

medium

low

medium

low

Exploited: No reports yet.
Needs login: No.
Needs a special setup: Not known from the sources.
Reachable from: internet.
Worst case: Attacker code runs inside the Chrome renderer sandbox after a page visit.
CVSS said: 8.8. The facts above say critical; we keep the sources' high until an analyst looks.

Who is affected

1 product

Know the next one before it finds you.

Add to Slack

Live › vulnerability › CVE-2026-113155

Go to dashboard

high8.8Vendor

Chrome: use-after-free in Glic lets a crafted page run code

Summary written from the sources below. Check the originals before acting.

CVSS 3.x

8.8

high

scored by 134c704f-9b21-4f2e-91b3-4a467353bcc0

known so far4 of 6

missing: primary source, exploitation

First public: Oct 20, 2026 UTC
Last modified: Oct 22, 2026
Status: open
Known exploitation: None reported
Public exploit: None on GitHub
EPSS: not scored

First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.

Why it is high, and not just CVSS

Likelihood → · Impact ↓

critical

high

medium

high

medium

low

medium

low

Exploited: No reports yet.
Needs login: No.
Needs a special setup: Not known from the sources.
Reachable from: internet.
Worst case: Attacker code runs inside the Chrome renderer sandbox after a page visit.
CVSS said: 8.8. The facts above say critical; we keep the sources' high until an analyst looks.

Who is affected

1 product

Know the next one before it finds you.

Add to Slack

Chrome: use-after-free in Glic lets a crafted page run code

Why it is high, and not just CVSS

Who is affected

Know the next one before it finds you.

Chrome: use-after-free in Glic lets a crafted page run code

Why it is high, and not just CVSS

Who is affected

Know the next one before it finds you.

How to check

The fix

Who had it, and when

What the sources say, verbatim

Sources