dbcve.org
ChromeWeb browser · Google

CVE-2026-14063

MEDIUM · 5.7 CVSS v3.1 Published 2026-06-30
Fix available
A fix is available. Upgrade to 150.0.7871.46 or later.
See remediation →
60/100
Remediation priority · Elevated
No privileges 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
Out of bounds read in Chromecast in Google Chrome prior to 150.0.7871.47 allowed a local attacker to obtain potentially sensitive information from process memory via malicious network traffic. (Chromium security severity: Low)

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

An out-of-bounds read vulnerability in Chromecast (a smart TV/streaming device running a modified Chrome OS) in Google Chrome versions prior to 150.0.7871.47 allows a local attacker with network access to read potentially sensitive data from process memory by sending specially crafted malicious network traffic.

MitigationUpdate Google Chrome to version 150.0.7871.47 or later on systems that manage Chromecast devices; for the Chromecast firmware itself, await and apply Google's security update.

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.46

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:A/AC:L/PR:N/UI:R/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. Identify if Google Chrome is installed
    On the system, check for Google Chrome installation - on Windows check Program Files/Google/Chrome/Application/chrome.exe, on macOS check /Applications/Google Chrome.app, on Linux check /usr/bin/google-chrome or /opt/google/chrome/google-chrome
    Affected if Google Chrome is installed and the version is less than 150.0.7871.46
  2. Determine the installed Chrome version
    Open Chrome, go to Settings > About Chrome, or navigate to chrome://settings/help, or run 'google-chrome --version' from command line
    Affected if The displayed version number is below 150.0.7871.46 (for example, 150.0.7871.45 or any earlier version)
  3. Verify network exposure of Chrome/Chromecast
    Check if the Chrome browser or Chromecast device is accessible on the network - for Chrome browser ensure it is not exposed to untrusted network segments; for Chromecast, check if the device is on a network with untrusted users
    Affected if The vulnerable Chrome version is installed and the device is accessible to a local network attacker

You are affected if Google Chrome version 150.0.7871.46 or earlier is installed on a system that can be reached by a local network attacker.

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.46 or later
Fixed in 150.0.7871.46
Interim mitigation

Update Google Chrome to version 150.0.7871.47 or later on systems that manage Chromecast devices; for the Chromecast firmware itself, await and apply Google's security update.

Recommended fix High confidence

Chrome 150.0.7871.47 or later

  1. Open Google Chrome and navigate to Settings > Help > About Google Chrome
  2. Verify the current installed version number
  3. If the version is earlier than 150.0.7871.47, click 'Update Google Chrome' to download and install the latest version
  4. Restart the browser to complete the update
  5. Alternatively, download the latest Chrome installer from the official Google Chrome download page and reinstall
Caveat Chrome auto-updates typically do not have breaking changes; enterprise environments should test for compatibility with internal applications before rolling out widely

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

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-14063 — 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-14063 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