MEDIUM 6.5

CVE-2026-13940: Chrome Cast Uninitialized Memory Disclosure – Patch Now

Google Chrome versions before 150.0.7871.47 contain a flaw in how the Cast feature handles uninitialized memory during type conversion. An attacker positioned on the same local network as a victim can send specially crafted network packets to trigger this bug, potentially reading sensitive data from Chrome's process memory without requiring user interaction or special privileges. The vulnerability is classified as medium severity.

Source data · NVD / CISA · public domain

CVSS
3.1 · 6.5 MEDIUM · CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Weaknesses (CWE)
CWE-457
Affected products
1 configuration(s)
Published / Modified
2026-06-30 / 2026-07-02

NVD description (verbatim)

Uninitialized Use in Cast in Google Chrome prior to 150.0.7871.47 allowed an attacker on the local network segment to obtain potentially sensitive information from process memory via malicious network traffic. (Chromium security severity: Medium)

2 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2026-13940 is an uninitialized use vulnerability (CWE-457) in Google Chrome's Cast implementation that occurs during a type-casting operation. The flaw allows an unauthenticated attacker on an adjacent network segment (AV:A) to cause Chrome to access uninitialized memory regions and leak their contents via malicious network traffic. The attack requires no user interaction and does not depend on complex or costly exploitation preconditions (AC:L). Impact is limited to confidentiality; the vulnerability does not enable code execution or denial of service. The Chromium project assigned this a Medium security severity rating.

Business impact

Information disclosure through memory leaks can expose sensitive user data including authentication tokens, cached credentials, personal information from open tabs, or encryption keys resident in Chrome's memory. While the attack requires network-level proximity, organizations with open wireless networks, compromised internal networks, or shared network segments face increased risk. This vulnerability does not directly enable data modification or service disruption, but the leaked information could facilitate secondary attacks such as session hijacking or credential theft.

Affected systems

Google Chrome versions prior to 150.0.7871.47 are affected. The vulnerability specifically impacts the Cast feature, so systems with Cast functionality enabled (which is the default in most Chrome deployments) are in scope. Desktop, laptop, and Chromebook installations running vulnerable versions on networks where an attacker can position themselves locally are at risk.

Exploitability

Exploitation requires the attacker to be on the same local network segment as the target; remote internet-based attacks are not possible. No special privileges, credentials, or user interaction are needed once network proximity is achieved. However, the attacker must craft malicious network packets specific to the Cast protocol or related network services, indicating some technical skill and preparation. The vulnerability is not known to be exploited in the wild (not listed on the KEV catalog) and no public exploit code has been published as of the vulnerability disclosure date.

Remediation

Update Google Chrome to version 150.0.7871.47 or later. The patch addresses the uninitialized memory access by ensuring proper initialization of variables in the Cast feature's type-casting operations. Users can verify their current Chrome version by navigating to Chrome menu > Help > About Google Chrome, which will automatically check for and install available updates. Organizations should prioritize patching systems in shared network environments or those exposed to untrusted local networks.

Patch guidance

Chrome automatically downloads and applies security updates; most users will be updated to version 150.0.7871.47 or newer within days of release. Administrators managing enterprise Chrome deployments via Chromium policies should verify the update has rolled out using the chrome://policy page or their management console. For users with auto-update disabled, manually check for updates via the About Chrome menu. No interim mitigations are documented; patching is the only remediation.

Detection guidance

Detection is challenging because the vulnerability is triggered by network packets on the local segment; traditional perimeter-based monitoring will not see the attack traffic. Network segmentation and monitoring of unexpected traffic on the Cast protocol (typically UDP on specific ports) from untrusted endpoints may provide signals. Endpoint detection and response (EDR) tools may observe suspicious network access patterns or unusual process memory reads if Cast-related processes behave anomalously, but signatures are not yet widely available. Organizations should focus on ensuring networks are properly segmented and that wireless access is secured to prevent unauthorized local network presence.

Why prioritize this

While rated CVSS 6.5 (medium), this vulnerability merits attention because: (1) Chrome is ubiquitous in enterprise and consumer environments; (2) local network access is increasingly feasible given BYOD policies, compromised guest networks, and supply-chain threats; (3) memory disclosure can directly lead to credential theft and lateral movement; (4) the fix is simple and automated. Patching should proceed on a standard schedule for medium-severity flaws, with higher priority for systems in open or untrusted network environments.

Risk score, explained

The CVSS 3.1 score of 6.5 reflects attack vector (adjacent network only, not internet-facing), low complexity exploitation, no privilege or user interaction requirement, and high confidentiality impact with no integrity or availability impact. The score appropriately captures the local-network-only attack surface that limits exposure compared to remotely exploitable vulnerabilities, while acknowledging the real privacy and security risk of uncontrolled memory disclosure.

Frequently asked questions

Can this vulnerability be exploited over the internet?

No. The vulnerability requires the attacker to be on the same local network segment as the target. It cannot be exploited remotely from the internet.

Does Chrome auto-update protect me from this issue?

Yes, Chrome's automatic update mechanism will deploy version 150.0.7871.47 or later, which patches the vulnerability. Most users will be protected within days of the update release. You can manually check for updates by going to Chrome menu > Help > About Google Chrome.

What data could be exposed by this vulnerability?

The vulnerability allows an attacker to read uninitialized memory from Chrome's process, which could contain cached passwords, session tokens, personal data from open web pages, or encryption keys depending on what is resident in memory at the time of the attack.

Is the vulnerability already being exploited in attacks?

As of the vulnerability publication date, it does not appear on the CISA Known Exploited Vulnerabilities (KEV) catalog, and no public exploits have been disclosed. However, organizations should still prioritize patching to reduce window of exposure.

This analysis is provided for informational purposes to help security teams prioritize vulnerability response. It is not a substitute for vendor advisories, security bulletins, or your organization's risk assessment processes. Verify all patch versions and compatibility with your environment against the official Google Chrome security release notes. SEC.co makes no warranty regarding the completeness or accuracy of exploitation scenarios or detection methods. If you discover evidence of active exploitation, contact your security team or law enforcement immediately. Source: NVD (public-domain), retrieved 2026-08-09. Analysis generated by SEC.co (claude-haiku-4-5).