dbcve.org
ChromeWeb browser · Google

CVE-2026-13937

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 policy enforcement in Passwords in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who had compromised the renderer process 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

Insufficient policy enforcement in Chrome's Passwords feature allowed a compromised renderer process to bypass same-origin policy protections and leak cross-origin data via crafted HTML pages. This is a browser-native vulnerability affecting the Passwords manager component prior to version 150.0.7871.47.

MitigationUpdate Google Chrome to version 150.0.7871.47 or later. For enterprise environments, deploy the update via centralized patch management and verify complete coverage across all affected 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. Verify Google Chrome is installed
    Check for Chrome installation by looking for chrome.exe in typical installation paths (e.g., C:\Program Files\Google\Chrome\Application\ on Windows, /Applications/Google Chrome.app on macOS, or via 'which google-chrome' on Linux). Alternatively, open Chrome and navigate to chrome://settings/help to confirm the browser is present.
    Affected if Google Chrome is not installed on the system
  2. Determine the installed Chrome version
    In Chrome, type chrome://version in the address bar and press Enter. Note the version number displayed (e.g., 150.0.7871.0). On Windows, you can also right-click chrome.exe, select Properties, and check the Details tab. On Linux, run 'google-chrome --version' in terminal.
    Affected if Unable to retrieve the installed version number
  3. Compare installed version against affected range
    Take the installed version number (e.g., 150.0.7871.0) and compare it numerically to the affected threshold 150.0.7871.47. Extract the major, minor, and build numbers for accurate comparison. Versions below 150.0.7871.47 are affected.
    Affected if Installed version is less than 150.0.7871.47 (e.g., 150.0.7871.0, 149.5.1234.56, etc.)
  4. Confirm Password Manager feature status
    In Chrome, go to chrome://settings/passwords. Verify whether the Password Manager is enabled (toggle switch at the top). This feature is enabled by default. The vulnerability exists in this component regardless of whether saved passwords are actively used.
    Affected if Password Manager is enabled (this is the default state and is required for the vulnerability to be exploitable)

A system is affected if Google Chrome is installed with a version lower than 150.0.7871.47 and the Password Manager feature is enabled, which is the default 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 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 update via centralized patch management and verify complete coverage across all affected endpoints.

Recommended fix High confidence

Chrome 150.0.7871.47 or later

  1. Open Google Chrome browser
  2. Click on the three-dot menu icon in the top-right corner
  3. Select 'Help' from the dropdown menu
  4. Click on 'About Google Chrome'
  5. The browser will automatically check for updates
  6. If version 150.0.7871.47 or later is available, click 'Update Google Chrome'
  7. Restart the browser to apply the update

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