dbcve.org
ChromeWeb browser · Google

CVE-2026-14048

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-30
Fix available
A fix is available. Upgrade to 150.0.7871.46 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
Use after free in Chromecast 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 a malicious peripheral. (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 · high confidence

A use-after-free vulnerability exists in the Chromecast component of Google Chrome versions prior to 150.0.7871.47. An attacker on the local network segment with a malicious peripheral can exploit this memory corruption issue to read potentially sensitive data from process memory after it has been freed.

MitigationUpdate Google Chrome to version 150.0.7871.47 or later to patch the vulnerability. If Chromecast firmware is separate, ensure it receives the corresponding 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
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 in browser
    Navigate to chrome://version in the Google Chrome address bar and locate the 'Version' field
    Affected if The displayed version number is less than 150.0.7871.46 (for example, 150.0.7871.0 or any earlier version)
  2. Check Chrome version via command line
    Run 'google-chrome --version' on Linux, 'C:\Program Files\Google\Chrome\Application\chrome.exe --version' on Windows, or 'open -a "Google Chrome" --version' on macOS
    Affected if The reported version is less than 150.0.7871.46
  3. Verify Chromecast component is present and enabled
    Check for the Cast extension or Media Router component. In Chrome, navigate to chrome://extensions and look for the 'Cast' extension, or check chrome://components for the 'Media Router' component
    Affected if The Cast extension or Media Router is present and enabled, and the Chrome version is vulnerable
  4. Check for active Cast sessions or configurations
    Click the three-dot menu in Chrome, look for the Cast icon in the toolbar, or check for any active Cast sessions via the system tray/notification area
    Affected if Chromecast functionality has been used or configured on the system, indicating the vulnerable component is active

A system is affected if Google Chrome version is below 150.0.7871.46 and the Chromecast/Media Router component is enabled or has been used on the local network.

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 to patch the vulnerability. If Chromecast firmware is separate, ensure it receives the corresponding security update.

Recommended fix High confidence

Chrome 150.0.7871.46 or later (specifically 150.0.7871.47 as noted in the official description)

  1. Check current Chrome version by navigating to chrome://settings/help or clicking Help > About Google Chrome
  2. If the version is earlier than 150.0.7871.46, click 'Update Google Chrome' to download and install the latest version
  3. Restart the browser after the update completes to apply the fix
  4. Verify the version now shows 150.0.7871.46 or later

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-14048 — 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-14048 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