dbcve.org
ChromeWeb browser · Google

CVE-2026-13990

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 DataTransfer in Google Chrome on Windows prior to 150.0.7871.47 allowed a remote attacker who had compromised the renderer process to perform UI spoofing 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 input validation in the DataTransfer API in Google Chrome on Windows before version 150.0.7871.47 allowed a remote attacker with an already compromised renderer process to perform UI spoofing by tricking users through a crafted HTML page.

MitigationUpdate Google Chrome to version 150.0.7871.47 or later on all Windows systems; organizations may use group policy or endpoint management tools to ensure consistent patching.

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
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. Verify Chrome is installed on Windows
    Open Control Panel > Programs and Features, or run 'Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome"' in PowerShell to check for Chrome installation
    Affected if Google Chrome is not found in the system registry or programs list, then this CVE does not apply
  2. Check installed Chrome version
    Launch Chrome, navigate to chrome://settings/help, or run '"C:\Program Files\Google\Chrome\Application\chrome.exe" --version' via command prompt
    Affected if The displayed version number is lower than 150.0.7871.47, indicating the installed version is within the affected range
  3. Confirm Windows platform
    Run 'winver' or check system properties to confirm the operating system is Windows
    Affected if The system is running Windows; this CVE only affects Chrome on Windows platforms prior to version 150.0.7871.47
  4. Understand exploit prerequisites
    This vulnerability requires a compromised renderer process, which is not a configurable condition. The DataTransfer API is a standard browser API enabled by default in Chrome and cannot be disabled through user settings.
    Affected if N/A - the API is always enabled; the vulnerability stems from insufficient input validation in Chrome's handling of DataTransfer API operations when a renderer process is compromised

If Google Chrome version 150.0.7871.47 or later is installed on Windows, the environment is not affected by this CVE.

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 on all Windows systems; organizations may use group policy or endpoint management tools to ensure consistent patching.

Recommended fix High confidence

Chrome 150.0.7871.47 or later

  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 check for updates and display the current version
  6. If an update is available, click 'Update Google Chrome'
  7. Restart the browser to complete the installation
  8. Verify the version is 150.0.7871.47 or later by returning to About Google 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
  • 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-13990 — 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-13990 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