Is CVE-2026-13782 exploited in the wild?

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

How severe is CVE-2026-13782?

Informational severity, with a CVSS score of 10, published 30 June 2026.

Which products and versions are affected?

Google Chrome Prior to 150.0.7871.47.

Is there a fix for CVE-2026-13782?

A patch was published on 2026-06-30: Fixed in Chrome version 150.0.7871.47. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-13782 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-13782?

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-13782: Google Chrome use after free in Browser sandbox escape

CVE-2026-13782 · Severity: info · CVSS 10 · Published 2026-06-30

Google Chrome, a widely used web browser, contains a critical security vulnerability that could allow an attacker to bypass the browser's security sandbox. If a user visits a specially crafted malicious website, an attacker who has already compromised the browser's rendering process could gain full control over the underlying computer system. This could lead to the theft of sensitive data, installation of malware, or complete disruption of business operations.

Technologies: Google Chrome. Vendors: Google.

Quick answers

Is CVE-2026-13782 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-13782 being exploited in the wild.
How severe is CVE-2026-13782?: Informational severity, with a CVSS score of 10, published 30 June 2026.
Which products and versions are affected?: Google Chrome Prior to 150.0.7871.47.
Is there a fix for CVE-2026-13782?: A patch was published on 2026-06-30: Fixed in Chrome version 150.0.7871.47. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-13782 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-13782?: 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.

Technical details

A use-after-free (UAF) vulnerability exists in the Browser component of Google Chrome prior to version 150.0.7871.47. The flaw is triggered when the browser incorrectly manages memory during the lifecycle of certain objects, allowing an attacker to reference memory after it has been freed. To exploit this, a remote attacker must first compromise the renderer process (e.g., via a separate vulnerability) and then entice a user to visit a malicious HTML page. Successful exploitation enables a sandbox escape, allowing the attacker to execute arbitrary code with the privileges of the browser process on the host operating system. Google has addressed this in the stable channel update to version 150.0.7871.47 and later.

Affected products

Google Chrome Prior to 150.0.7871.47

Timeline

2026-05-26: disclosed: Reported to Google by internal researchers.
2026-06-30: patched: Fixed in Chrome version 150.0.7871.47.
2026-06-30: advisory: Public advisory published by Google and NVD.

References

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