# CVE-2026-13779 — Google Chrome

> As of 2026-07-02, CVE-2026-13779 is a HIGH-severity vulnerability in Google Chrome, CVSS v3.1 8.1, EPSS 0.3% (31.3th percentile). Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2026-13779, most recently “Chrome 151 Security Update Patches 382 Vulnerabilities, Including 15 Critical Memory-Corruption Flaws (CVE-2026-13774 to CVE-2026-13788)”.

**Last updated:** 2026-07-02

## What is CVE-2026-13779?

Use after free in Chromoting in Google Chrome on ChromeOS prior to 150.0.7871.47 allowed a remote attacker to execute arbitrary code via malicious network traffic. (Chromium security severity: Critical)

The record classifies CVE-2026-13779 under weakness class [CWE-416](https://intel.threadlinqs.com/cwe/CWE-416). Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction, and has high impact on confidentiality, integrity, availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 102 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 8.1 — HIGH (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **EPSS (FIRST):** 0.3% probability of exploitation in the next 30 days, higher than 31.3% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 7.3/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-06-30, last modified 2026-07-02

## Is CVE-2026-13779 being exploited?

Weaponised exploit code for CVE-2026-13779 is publicly available. 1 public proof-of-concept repository is tracked for this identifier. It currently carries a trending score of 25 in the Threadlinqs vulnerability feed.

- [trickest/cve](https://github.com/trickest/cve/blob/main/2026/CVE-2026-13779.md) (trickest)

## Affected products and versions

- [Google](https://intel.threadlinqs.com/vendors/google): Chrome

## How to fix CVE-2026-13779

Vendor advisory: [https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html](https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html). Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

## Threat activity tracking CVE-2026-13779

1 tracked threat in the Threadlinqs corpus references CVE-2026-13779, either in the campaign’s CVE list or as an indicator on the campaign record.

- [Chrome 151 Security Update Patches 382 Vulnerabilities, Including 15 Critical Memory-Corruption Flaws (CVE-2026-13774 to CVE-2026-13788)](https://intel.threadlinqs.com/threat/TL-2026-1026) — CRITICAL · 2026-07-01

## Sources

Enriched from CVE.org, NVD, FIRST EPSS, GitHub Security Advisories, public proof-of-concept repositories. Last verified by Threadlinqs on 2026-10-10. This product uses the NVD API but is not endorsed or certified by the NVD.

**Other references**

- [chromereleases.googleblog.com](https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html)
- [issues.chromium.org](https://issues.chromium.org/issues/513222854)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-13779
Full detection coverage and IOCs for threats exploiting CVE-2026-13779 via the Threadlinqs MCP server (Purple tier): https://intel.threadlinqs.com/mcp