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

Run chrome://version in Chrome and compare the version with 156.0.8078.47. On Linux or macOS: google-chrome --version (or the installed Chrome app's version).

What is the fix for CVE-2026-113065?

Update Google Chrome to 156.0.8078.47 or later and restart the browser. For managed fleets, push the update through the enterprise update policy.

Who is not affected by CVE-2026-113065?

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

Live › vulnerability › CVE-2026-113065

Go to dashboard

high8.8Vendor

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

A use-after-free bug in Chrome's Media component lets a remote attacker run arbitrary code inside the browser sandbox when a victim opens a crafted HTML page. The sandbox limits what that code can do on the machine, but it is still code execution from a web page.

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: Code runs inside the browser sandbox after a victim opens 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-113065

Go to dashboard

high8.8Vendor

Chrome: media use-after-free lets a crafted 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 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: Code runs inside the browser sandbox after a victim opens 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: media use-after-free lets a crafted 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: media use-after-free lets a crafted 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