dbcve.org
ChromeWeb browser · Google

CVE-2026-13940

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-30
Fix available
A fix is available. Upgrade to 150.0.7871.47 or later.
See remediation →
70/100
Remediation priority · Elevated
No privileges Zero-click 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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)

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is an uninitialized memory use vulnerability in Google Chrome's Cast component. An attacker positioned on the local network segment can send malicious network traffic to trigger the vulnerability, causing Chrome to read uninitialized memory that may contain sensitive process information and leak it via network responses.

MitigationUpdate Google Chrome to version 150.0.7871.47 or later to patch the vulnerability. Additionally, review network segmentation to limit exposure from local network attackers.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ChromeWeb browser
Affected:< 150.0.7871.47

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Chrome version
    Open chrome://version in the Chrome address bar or go to Chrome Menu > Help > About Google Chrome to view the version number
    Affected if Version is below 150.0.7871.47 (for example, 150.0.7871.0 or any earlier version)
  2. Verify Cast component is present
    Look for the Cast icon in the Chrome toolbar (typically in the top-right corner near the address bar), or check chrome://extensions for Cast-related extensions
    Affected if Cast extension or Cast icon is visible and enabled in the browser
  3. Confirm Chrome is used in an environment with local network access
    Review whether Chrome is running on a system connected to a network segment where untrusted local attackers could send traffic (such as shared Wi-Fi, corporate LAN with multiple users, or untrusted home networks)
    Affected if Chrome runs on a system with local network exposure to potentially untrusted devices
  4. Check for recent Chrome network activity
    Open Chrome DevTools > Network tab while Chrome is running, or monitor network connections using system tools to observe if Cast-related network endpoints are responding
    Affected if Cast component is actively making network requests that could potentially return leaked memory data

You are affected if Chrome version is below 150.0.7871.47, the Cast component is enabled, and the system is on a network where local attackers could send malicious traffic to trigger the uninitialized memory read.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 150.0.7871.47 or later
Fixed in 150.0.7871.47
Interim mitigation

Update Google Chrome to version 150.0.7871.47 or later to patch the vulnerability. Additionally, review network segmentation to limit exposure from local network attackers.

Recommended fix High confidence

150.0.7871.47 or later

  1. Open Google Chrome and navigate to chrome://settings/help to check the current version
  2. If Chrome version is below 150.0.7871.47, click 'Update Google Chrome' to install the latest version
  3. Alternatively, download the latest stable Chrome from https://www.google.com/chrome and reinstall
  4. Restart Chrome after the update completes
  5. Verify the version is now 150.0.7871.47 or higher via chrome://settings/help

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-13940 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-13940 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data