Is CVE-2026-76031 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-76031 being exploited in the wild.

How severe is CVE-2026-76031?

Informational severity, published 30 October 2026.

Which products and versions are affected?

Google Chrome prior to 156.0.8078.79.

Is there a fix for CVE-2026-76031?

Yes: fixed in Chrome 156.0.8078.79 and later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-76031 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-76031?

Check whether you run Google Chrome at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-76031: Google Chrome use after free in Input

CVE-2026-76031 · Severity: info · Published 2026-10-30

Google Chrome is a web browser used by billions of users worldwide. A use-after-free vulnerability in the Input component could allow a remote attacker to execute arbitrary code within Chrome's sandbox by tricking a user into visiting a malicious webpage. Successful exploitation could lead to browser compromise and potential data theft.

Technologies: Google Chrome. Vendors: Google.

Quick answers

Is CVE-2026-76031 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-76031 being exploited in the wild.
How severe is CVE-2026-76031?: Informational severity, published 30 October 2026.
Which products and versions are affected?: Google Chrome prior to 156.0.8078.79.
Is there a fix for CVE-2026-76031?: Yes: fixed in Chrome 156.0.8078.79 and later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-76031 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-76031?: Check whether you run Google Chrome at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: Chrome 156.0.8078.79 and later

Technical details

A use-after-free vulnerability exists in Chrome's Input component that can be triggered via a crafted HTML page. The vulnerability allows remote code execution within the browser sandbox without requiring user authentication or additional interaction beyond viewing the malicious page. This is classified as a High severity issue by the Chromium security team.

Affected products

Google Chrome prior to 156.0.8078.79

Timeline

2026-10-29: disclosed
2026-10-29: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.