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

Run chrome://version in the browser and compare the version with 156.0.8078.47. On managed fleets, check the Chrome version reported by endpoint management.

What is the fix for CVE-2026-113119?

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

Who is not affected by CVE-2026-113119?

Not affected if: already-on-156.0.8078.47-or-later, non-windows-platforms.

Live › vulnerability › CVE-2026-113119

Go to dashboard

high8.8Vendor

Chrome on Windows: use-after-free lets a web page run code in sandbox

A use-after-free bug in Chrome's Network component on Windows lets a remote attacker run arbitrary code inside the browser sandbox via a crafted HTML page. The sources rate it high (CVSS 8.8) and do not say it is exploited in the wild.

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 23, 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 victim visits a 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-113119

Go to dashboard

high8.8Vendor

Chrome on Windows: use-after-free lets a web page run code in sandbox

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 23, 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 victim visits a 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

Chrome on Windows: use-after-free lets a web page run code in sandbox

Why it is high, and not just CVSS

Who is affected

Know the next one before it finds you.

Chrome on Windows: use-after-free lets a web page run code in sandbox

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