dbcve.org
ChromeWeb browser · Google

CVE-2026-13893

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-30
Fix available
A fix is available. Upgrade to 150.0.7871.47 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges 7 weeks old

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 WebUI in Google Chrome prior to 150.0.7871.47 allowed a remote attacker to leak cross-origin data via malicious network traffic. (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 Google Chrome's WebUI component allows a remote attacker to leak cross-origin data via malicious network traffic. The vulnerability stems from improper input handling in the WebUI that fails to properly enforce same-origin policy, potentially exposing sensitive data from other origins to an attacker-controlled context.

MitigationUpdate Google Chrome to version 150.0.7871.47 or later. For enterprise environments, deploy the browser update through standard patch management processes and verify coverage across managed endpoints.

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

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. Identify Chrome installation location
    Locate the Chrome executable (chrome.exe on Windows, Google Chrome.app on macOS, or chrome on Linux) - typically in Program Files (Windows), /Applications (macOS), or /usr/bin (Linux)
    Affected if Chrome is installed on the system
  2. Determine installed Chrome version
    Open Chrome, click the three-dot menu, select Help > About Google Chrome, or navigate to chrome://settings/help. The version number is displayed on that page.
    Affected if Version number displayed is less than 150.0.7871.47 (for example, 150.0.7871.0, 149.x.x.x, or any earlier version)
  3. Confirm WebUI component is reachable
    This vulnerability affects the WebUI component handling network traffic. Verify Chrome can process network requests by attempting to load any website. The WebUI processes URLs including chrome:// URLs.
    Affected if Chrome processes network requests and the WebUI component is active (default behavior)
  4. Check for same-origin policy enforcement
    The vulnerability allows cross-origin data leakage via the WebUI. This is a built-in component behavior. No specific configuration toggle exists to enable or disable this. The flaw exists in how Chrome processes certain WebUI requests.
    Affected if Chrome's WebUI handles network traffic (this is default behavior for any Chrome installation)

A user is affected if they have Google Chrome installed with a version number less than 150.0.7871.47 and use Chrome to browse the web, as the vulnerable WebUI component processes network traffic by default.

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

Update Google Chrome to version 150.0.7871.47 or later. For enterprise environments, deploy the browser update through standard patch management processes and verify coverage across managed endpoints.

Recommended fix High confidence

Chrome 150.0.7871.47 or later

  1. Open Google Chrome and navigate to chrome://settings/help to check for updates
  2. Chrome will automatically check for and download the latest version. If version 150.0.7871.47 or later is available, click 'Update Google Chrome'
  3. After the update completes, click 'Relaunch' to restart Chrome and apply the security fix
  4. Alternatively, download the latest stable Chrome version directly from the official Google Chrome website if automatic updates are unavailable
Caveat Browser updates typically have minimal breaking changes; however, some extensions may require re-authentication or settings could reset to defaults

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