dbcve.org
ChromeWeb browser · Google

CVE-2026-11194

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
Inappropriate implementation in Network in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to leak cross-origin data 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 · high confidence

A cross-origin data leak vulnerability in Google Chrome's Network component allowed a remote attacker to leak sensitive data from other origins through a specially crafted HTML page due to an inappropriate implementation in how the browser handles network requests and cross-origin policies.

MitigationUpgrade Google Chrome to version 149.0.7827.53 or later. Organizations should deploy the patched browser version to endpoint devices through their software distribution or endpoint management tools.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 if Google Chrome is installed
    Locate the Chrome executable: on Windows typically C:\Program Files\Google\Chrome\Application\chrome.exe, on macOS /Applications/Google Chrome.app, or on Linux via 'which google-chrome' or 'which chromium' in terminal
    Affected if Google Chrome or Chromium browser is present on the system
  2. Determine the installed Chrome version
    Open chrome://version in the browser address bar or run 'google-chrome --version' (or 'chromium --version' for Chromium-based browsers) in the command line
    Affected if A version number is returned showing the installed browser version
  3. Compare installed version against affected range
    Compare the version number from the previous step to the affected range: versions below 149.0.7827.53 are vulnerable; version 149.0.7827.53 and later are patched
    Affected if Installed version is less than 149.0.7827.53 (for example, 148.5.1234.56 or any earlier major version)
  4. Verify the Network component is in use
    This vulnerability affects the Network component which handles HTTP/HTTPS requests. Confirm the browser is used for web browsing with network access. No specific config check needed as the Network component is always active during browser use
    Affected if The browser is used for web browsing, which activates the vulnerable Network component

The environment is affected if Google Chrome or a Chromium-based browser is installed with a version lower than 149.0.7827.53 and is used for web browsing.

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

Upgrade Google Chrome to version 149.0.7827.53 or later. Organizations should deploy the patched browser version to endpoint devices through their software distribution or endpoint management tools.

Recommended fix High confidence

Chrome version 149.0.7827.53 or later

  1. Open Google Chrome browser
  2. Navigate to the Chrome menu (three dots) in the top-right corner
  3. Select 'Help' > 'About Google Chrome'
  4. The browser will check for updates and display the current version
  5. If an update is available, Chrome will automatically download and prompt you to restart
  6. Click 'Restart' to complete the update to version 149.0.7827.53 or later
  7. Alternatively, download the latest Chrome from the official Google website: https://www.google.com/chrome/

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