dbcve.org
ChromeWeb browser · Google

CVE-2026-11241

HIGH · 8.0 CVSS v3.1 Published 2026-06-05
Fix available
A fix is available. Upgrade to 149.0.7827.53 or later.
See remediation →
83/100
Remediation priority · High
No privileges

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
Insufficient validation of untrusted input in Cast in Google Chrome prior to 149.0.7827.53 allowed an attacker on the local network segment to perform privilege escalation via a crafted HTML page. (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

Insufficient validation of untrusted input in Chrome's Cast component allows an attacker on the local network segment to perform privilege escalation by tricking a user into visiting a crafted HTML page. The vulnerability exists in versions prior to 149.0.7827.53.

MitigationUpdate Google Chrome to version 149.0.7827.53 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:< 149.0.7827.53

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
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:R/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 C:\Program Files\Google\Chrome\Application\chrome.exe or look for Chrome in Add/Remove Programs. On Mac, check /Applications/Google Chrome.app. On Linux, run which google-chrome or check /opt/google/chrome/google-chrome.
    Affected if Google Chrome is not found on the system, so the CVE does not apply.
  2. Determine installed Chrome version
    Open Chrome and navigate to chrome://version, or run 'google-chrome --version' from command line (Linux/Mac). On Windows, you can also right-click chrome.exe > Properties > Details > File Version.
    Affected if Unable to determine the installed version.
  3. Compare version to affected range
    Compare the installed version number to 149.0.7827.53. Note that version numbers are compared as numerical components; any version starting with 149.0.7827.53 or higher is not affected, while versions like 149.0.7827.52, 148.x.x.x, or earlier are affected.
    Affected if The installed version is less than 149.0.7827.53.
  4. Verify Cast component status (optional context)
    In Chrome, click the three-dot menu > Settings > Cast. Or check if Cast icon appears in the browser toolbar. The vulnerability requires the Cast component to be accessible; however, the specific status check depends on whether the Cast API or UI is reachable by local network attackers.
    Affected if Cast is actively enabled and accessible, combined with an affected Chrome version.

The environment is affected if Google Chrome is installed with a version lower than 149.0.7827.53, regardless of Cast feature status, since the vulnerable code exists in the Cast component regardless of user configuration.

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.53 or later
Fixed in 149.0.7827.53
Interim mitigation

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

Recommended fix High confidence

149.0.7827.53

  1. Open Google Chrome browser
  2. Click the three-dot menu icon in the top-right corner
  3. Select 'Help' from the dropdown menu
  4. Click 'About Google Chrome'
  5. Chrome will automatically check for updates and download version 149.0.7827.53 or later
  6. Click 'Relaunch' or 'Restart' to apply the update
  7. Verify the update by returning to About Google Chrome and confirming the version is 149.0.7827.53 or higher

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