dbcve.org
ChromeWeb browser · Google

CVE-2026-7349

HIGH · 7.5 CVSS v3.1 Published 2026-04-28
Fix available
A fix is available. Upgrade to 147.0.7727.138 or later.
See remediation →
80/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 147.0.7727.138 allowed an attacker on the local network segment to execute arbitrary code inside a sandbox 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 · high confidence

A use-after-free vulnerability exists in the Cast component of Google Chrome versions prior to 147.0.7727.138. An attacker on the local network segment can send malicious network traffic to trigger this memory corruption flaw, potentially allowing execution of arbitrary code within the Chrome sandbox.

MitigationUpdate Google Chrome to version 147.0.7727.138 or later to remediate this vulnerability.

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

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

CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/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. Check if Google Chrome is installed
    On Windows: Check for Chrome in Program Files or via Registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome. On macOS: Check /Applications/Google Chrome.app. On Linux: Check for google-chrome package via package manager or /usr/bin/google-chrome.
    Affected if Google Chrome is not found on the system, this CVE does not apply.
  2. Determine installed Chrome version
    Open Chrome and navigate to chrome://version, or run 'google-chrome --version' from command line on Linux/Mac, or check the Version value in the Windows Registry uninstall key.
    Affected if The installed version number is lower than 147.0.7727.138.
  3. Verify Cast component is enabled
    In Chrome, go to chrome://flags and search for 'Cast' or check chrome://settings/handlers to see if Cast devices are being detected. The vulnerability only affects systems where the Cast feature is active.
    Affected if The Cast feature is enabled and actively detecting Cast devices on the network.
  4. Assess local network exposure
    Determine whether the system is on a network segment where untrusted local attackers could send malicious network traffic to trigger the Cast component. This includes shared Wi-Fi networks, Ethernet hubs, or untrusted LAN segments.
    Affected if The system is accessible from untrusted local network segments.

A user is affected if they have Google Chrome installed with a version prior to 147.0.7727.138, the Cast component is enabled, and the system is on a network where a local attacker could send malicious traffic to the Cast service.

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

Update Google Chrome to version 147.0.7727.138 or later to remediate this vulnerability.

Recommended fix High confidence

Chrome 147.0.7727.138 or later (stable channel)

  1. Open Google Chrome and navigate to Settings > Help > About Google Chrome (or enter chrome://settings/help in the address bar)
  2. Chrome will automatically check for available updates
  3. If update 147.0.7727.138 or later is available, click 'Update Google Chrome' to download and install it
  4. Restart Chrome completely to apply the update
  5. After restart, return to About Google Chrome to confirm the version number is 147.0.7727.138 or higher
Caveat Minimal risk - Chrome stable updates are backward-compatible and focus on security fixes; some legacy features may be deprecated over multiple releases

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
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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