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

Open chrome://settings/help, or chrome://version, and check the version. Anything below 156.0.8078.47 (Linux) or 156.0.8078.47/.48 (Windows/Mac) is exposed. For Debian Chromium run: dpkg -l chromium. Other Chromium-based browsers need their own vendor update.

What is the fix for CVE-2026-113290?

Update Chrome to 156.0.8078.47 or later (156.0.8078.47/.48 on Windows and Mac), then relaunch the browser. On Debian trixie, install chromium 156.0.8078.47-1~deb13u1 (DSA-6577-1). The Debian tracker listed bookworm and forky as vulnerable when I read it.

Who is not affected by CVE-2026-113290?

Not affected if: already-on-156.0.8078.47-or-later, managed-hosting.

Live › vulnerability › CVE-2026-113290

Go to dashboard

medium8.8Runtime

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

A use-after-free in Chrome's Input component lets a crafted HTML page potentially run code inside the renderer sandbox. Chromium rates it Medium. Google found it internally. No exploitation or public PoC is known. Reaching the rest of the system would take a separate sandbox escape, and none is known.

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

CVSS 3.x

8.8

medium

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

known so far5 of 6

missing: exploitation

First public: Oct 20, 2026 UTC
Last modified: Oct 24, 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 medium, 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: Code runs inside the browser sandbox after a user visits a crafted page.
CVSS said: 8.8. The facts above say critical; we keep the sources' medium until an analyst looks.

Who is affected

1 product

Know the next one before it finds you.

Add to Slack

Live › vulnerability › CVE-2026-113290

Go to dashboard

medium8.8Runtime

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

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

CVSS 3.x

8.8

medium

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

known so far5 of 6

missing: exploitation

First public: Oct 20, 2026 UTC
Last modified: Oct 24, 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 medium, 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: Code runs inside the browser sandbox after a user visits a crafted page.
CVSS said: 8.8. The facts above say critical; we keep the sources' medium 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 Input lets a web page run code

Why it is medium, and not just CVSS

Who is affected

Know the next one before it finds you.

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

Why it is medium, 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