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

Run chrome://version in Chrome and compare the version to 156.0.8078.47. On managed machines, check the Chrome version across the fleet with your MDM or endpoint tool.

What is the fix for CVE-2026-113114?

Update Google Chrome to 156.0.8078.47 or later. Restart the browser after the update so the new version is running.

Who is not affected by CVE-2026-113114?

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

Live › vulnerability › CVE-2026-113114

Go to dashboard

high8.8Other

Google Chrome: use-after-free in sign-in lets a web page run code

A memory-corruption bug in Chrome's SignIn component lets a remote attacker run code inside the browser sandbox by serving a crafted HTML page. Sources rate it high (CVSS 8.8) but Chromium's own rating is Low, and the sandbox limits what the code can reach.

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 21, 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: No.
Reachable from: internet.
Worst case: Attacker code runs inside the Chrome sandbox after a visit to a crafted page.
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-113114

Go to dashboard

high8.8Other

Google Chrome: use-after-free in sign-in lets a web 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 21, 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: No.
Reachable from: internet.
Worst case: Attacker code runs inside the Chrome sandbox after a visit to a crafted page.
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

Google Chrome: use-after-free in sign-in lets a web page run code

Why it is high, and not just CVSS

Who is affected

Know the next one before it finds you.

Google Chrome: use-after-free in sign-in lets a web 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