dbcve.org
ChromeWeb browser · Google

CVE-2026-12014

HIGH · 8.3 CVSS v3.1 Published 2026-06-11
Fix available
A fix is available. Upgrade to 149.0.7827.115 or later.
See remediation →
88/100
Remediation priority · High
No privileges Zero-click

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 Cast in Google Chrome prior to 149.0.7827.115 allowed an attacker on the local network segment to potentially perform a sandbox escape via malicious network traffic. (Chromium security severity: High)

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

Use-after-free vulnerability in Google Chrome's Cast component prior to version 149.0.7827.115 allows an attacker on the local network segment to send malicious network traffic and potentially achieve sandbox escape through memory corruption.

MitigationUpgrade Google Chrome to version 149.0.7827.115 or later on all affected systems.

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:< 149.0.7827.115

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
High
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

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. Determine installed Chrome version
    Open chrome://version in the Chrome browser or run 'google-chrome --version' (Linux/macOS) or check the application version via Help > About Google Chrome (Windows)
    Affected if The reported version number is lower than 149.0.7827.115
  2. Verify Cast component status
    Navigate to chrome://components in Chrome and locate the 'Cast' or 'Media Router' component entry
    Affected if The Cast component is present and enabled (any version below 149.0.7827.115 indicates vulnerability)
  3. Check for active Cast extensions
    Navigate to chrome://extensions and look for the 'Cast' extension or any extension with 'Chromecast' or 'Cast' in the name that is enabled
    Affected if A Cast or Chromecast extension is installed and enabled on a Chrome version below 149.0.7827.115
  4. Assess network exposure
    Determine if the system is on a shared local network segment (such as a home network, office LAN, or public WiFi) where untrusted devices could send network traffic to the host
    Affected if The system is on a local network segment with untrusted devices and Chrome version is below 149.0.7827.115 with Cast enabled

You are affected if Google Chrome version is below 149.0.7827.115 AND the Cast component is enabled AND the system is on a network where an attacker could send malicious traffic to your machine.

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 149.0.7827.115 or later
Fixed in 149.0.7827.115
Interim mitigation

Upgrade Google Chrome to version 149.0.7827.115 or later on all affected systems.

Recommended fix High confidence

Chrome 149.0.7827.115 or later (stable channel)

  1. Open Google Chrome and navigate to Chrome Menu > Help > About Google Chrome
  2. Alternatively, navigate to chrome://settings/help
  3. Chrome will automatically check for updates and display the current version
  4. If the version is below 149.0.7827.115, click 'Update Google Chrome' if prompted
  5. Restart the browser to complete the installation of the update
  6. Verify the update was successful by returning to the About page and confirming version 149.0.7827.115 or later is installed

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

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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