CVE Intelligence
Analysis AI-assisted

CVE-2026-13798: Google Chrome Chromecast Heap Buffer Overflow (CWE-122)

A heap buffer overflow in the Chromecast component of Google Chrome before 150.0.7871.47 could let a remote attacker who already compromised the renderer process attempt a sandbox escape through a crafted HTML page. The CNA scores it 9.6 (CVSS v3.1, critical), but the sources consulted show no confirmed exploitation. Updating Chrome to a fixed build is the main remediation step.

Published Oct 13, 2026 · Updated Oct 13, 2026 · Ler em português

Overview

CVE-2026-13798 is a heap-based buffer overflow (CWE-122) in the Chromecast component of Google Chrome. According to the record, a remote attacker who had already compromised the renderer process could potentially perform a sandbox escape using a crafted HTML page. Chromium rates the issue High severity.

Impact

  • Confirmed by the record: the potential outcome is a sandbox escape, and it requires prior compromise of the renderer process.
  • The CVSS v3.1 vector in the record describes a network attack vector, low complexity, no privileges required, user interaction required, scope changed, and high impact on confidentiality, integrity and availability.
  • The CNA assigned a score of 9.6, which is rated critical.

Affected products and versions

  • Google Chrome. The affected range in the record is versions before 150.0.7871.46.
  • The description names 150.0.7871.47 as the boundary. These two values differ, so verify the exact fixed build in the Chrome stable channel release notes.

Exploitation status

The record shows no CISA KEV listing for this CVE. No confirmed exploitation appears in the sources consulted. The record gives an EPSS probability of 0.00373 and a percentile of 0.29416.

Remediation and mitigation

  • Update Google Chrome to the latest stable build, at minimum the build that the release notes identify as fixed.
  • Keep automatic updates enabled, and confirm that managed endpoints have received the update and restarted the browser.
  • Review the Chromium issue tracker entry for further context, noting that its access is restricted.

Detection guidance

  • Inventory Chrome installations and record build numbers, flagging any build below the fixed threshold.
  • Use endpoint management reports to find browsers that have not restarted after an update.
  • Monitor for unusual renderer crashes or sandbox-related events in endpoint telemetry as a defensive signal only.

Limitations of the available information

  • The record contains no fixes list, so the fixed version comes only from the description.
  • The affected version string (before 150.0.7871.46) conflicts with the description (before 150.0.7871.47).
  • The Chromium issue tracker reference is tagged as requiring permissions, so its content was not reviewed.
  • No vendor-provided proof of concept or technical details beyond the description were available, and none are provided here.

Frequently asked questions

What is CVE-2026-13798?

It is a heap-based buffer overflow in the Chromecast component of Google Chrome before 150.0.7871.47. According to the record, it could allow a sandbox escape by an attacker who had already compromised the renderer process.

Is this vulnerability being actively exploited?

The record shows no CISA KEV listing, and no confirmed exploitation appears in the sources consulted.

What should administrators do?

Update Google Chrome to the latest stable build, confirm the fixed version in the release notes, and verify that managed endpoints have restarted the browser.

This analysis was drafted with AI assistance from verified source data and automatically checked against it.