Skip to main content

Google Chrome EUVDEUVD-2026-40570

| CVE-2026-13884 HIGH
Heap-based Buffer Overflow (CWE-122)
2026-06-30 chrome-cve-admin@google.com GHSA-4pmm-4ff4-v6hc
8.8
CVSS 3.1 · Vendor: google
Share

Severity by source

Vendor (google) PRIMARY
8.8 HIGH
AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
8.8 HIGH

Cast traffic requires adjacent-network position (AV:A) with no auth or interaction; a heap overflow yielding code execution gives full C/I/A impact.

3.1 AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
4.0 AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
SUSE
HIGH
qualitative
Red Hat
8.8 MEDIUM
qualitative

Primary rating from Vendor (google).

CVSS VectorVendor: google

Attack Vector
Adjacent
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

4
Analysis Generated
Jul 01, 2026 - 14:25 vuln.today
CVSS changed
Jul 01, 2026 - 14:22 NVD
8.8 (HIGH)
CVE Published
Jun 30, 2026 - 23:17 cve.org
UNKNOWN (no severity yet)
CVE Published
Jun 30, 2026 - 23:17 cve.org
HIGH 8.8

DescriptionCVE.org

Integer overflow in Chromecast in Google Chrome prior to 150.0.7871.47 allowed a local attacker to execute arbitrary code via malicious network traffic. (Chromium security severity: Medium)

AnalysisAI

Heap-based integer overflow in Google Chrome's Chromecast component allows an adjacent-network attacker to achieve arbitrary code execution against browsers running versions prior to 150.0.7871.47. The flaw is reachable via crafted malicious network traffic and carries a high CVSS of 8.8; Google has shipped a stable-channel fix, and no public exploit has been identified at time of analysis. Chromium rates the underlying issue as Medium severity despite the high CVSS, reflecting the adjacency and interaction constraints.

Technical ContextAI

The vulnerability lives in Chrome's Chromecast (Cast) subsystem, which handles device discovery and media-streaming session negotiation over the local network. CWE-122 (heap-based buffer overflow) here stems from an integer overflow: a length or size value derived from attacker-controlled network data wraps around, leading to an undersized heap allocation followed by an out-of-bounds write. Corrupting adjacent heap metadata or object pointers in Chrome's renderer/browser process memory is the classic primitive that enables control-flow hijack and code execution. Because Cast operates on data received from the network rather than page content, the attack surface is the streaming/discovery protocol parser rather than the JavaScript engine.

RemediationAI

Vendor-released patch: update Google Chrome to 150.0.7871.47 or later via the Stable Channel Update; most installations receive this through Chrome's automatic updater, so ensure auto-update is enabled and restart the browser to apply it (verify via chrome://settings/help). See the advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html and issue https://issues.chromium.org/issues/500077014. As a compensating control until patched, restrict exposure to the Cast attack surface: disable Chromecast/Media Router (set the MediaRouterEnable / EnableMediaRouter enterprise policy to false, or block the cast:// feature), which prevents discovery/streaming traffic from reaching the vulnerable parser at the cost of losing Cast-to-device functionality. Additionally, isolate untrusted devices from user segments and block mDNS/Cast discovery ports (UDP 5353 and Cast TCP 8008/8009/8443) at network boundaries to reduce adjacent-network reachability, accepting that this breaks legitimate casting on those segments.

Vendor StatusVendor

SUSE

Severity: Important
Product Status
SUSE Package Hub 15 SP7 Fixed
openSUSE Tumbleweed Fixed
SUSE Package Hub 15 SP7 Affected

Share

EUVD-2026-40570 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy