dbcve.org
ChromeWeb browser · Google

CVE-2026-11069

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-04
Fix available
A fix is available. Upgrade to 149.0.7827.53 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable 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 a remote attacker to bypass same origin policy via a crafted HTML page. (Chromium security severity: Medium)

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

Insufficient validation of untrusted input in Chrome's Cast component prior to version 149.0.7827.53 allows a remote attacker to bypass Same Origin Policy restrictions via a crafted HTML page. This could enable malicious pages to access resources from other origins that should be protected by SOP.

MitigationUpdate Google Chrome to version 149.0.7827.53 or later. Organizations should ensure automated browser update mechanisms are enabled or deploy managed Chrome updates via enterprise policies.

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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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. Confirm Google Chrome is installed
    Open Chrome and navigate to chrome://version or click Help > About Google Chrome to see the installed version
    Affected if Chrome is not installed - the vulnerability only applies to Google Chrome, not other browsers
  2. Check the installed Chrome version against affected range
    Note the full version number displayed in chrome://version and compare it to 149.0.7827.53
    Affected if The installed version is less than 149.0.7827.53 - versions below this contain the unpatched vulnerability
  3. Verify if Cast functionality is enabled
    Navigate to chrome://settings/cast or look for the Cast icon in the Chrome toolbar/menu
    Affected if Cast is actively enabled or the Cast extension is installed - the vulnerability exists in the Cast component itself, so the attack surface requires Cast to be accessible
  4. Check for recent browser activity
    Review browsing history or ask users if they have visited or shared content via Cast-enabled web pages recently
    Affected if Users have used Cast features - the SOP bypass allows a crafted page to access cross-origin resources through the Cast component

A user is affected if they are running Google Chrome versions below 149.0.7827.53 AND have Cast functionality accessible in their browser, as the vulnerability is specifically in the Cast component's handling of cross-origin requests.

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. Organizations should ensure automated browser update mechanisms are enabled or deploy managed Chrome updates via enterprise policies.

Recommended fix High confidence

149.0.7827.53 or later

  1. Open Google Chrome and navigate to Settings > Help > About Google Chrome to check for updates
  2. If an update is available, download and install version 149.0.7827.53 or later
  3. Alternatively, download the latest stable Chrome version from the official Google Chrome website
  4. Restart the browser after the update completes
  5. Verify the version by navigating to chrome://settings/help to confirm the version is 149.0.7827.53 or higher
Caveat Chrome upgrades typically do not introduce breaking changes for end users; however, some older extensions or system configurations may require attention after updating

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