dbcve.org
ChromeWeb browser · Google

CVE-2026-13961

MEDIUM · 5.3 CVSS v3.1 Published 2026-06-30
Fix available
A fix is available. Upgrade to 150.0.7871.46 or later.
See remediation →
60/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 DevTools in Google Chrome on Windows prior to 150.0.7871.47 allowed a remote attacker who convinced a user to engage in specific UI gestures to obtain potentially sensitive information from process memory 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 DevTools on Windows prior to version 150.0.7871.47 allows a remote attacker to obtain potentially sensitive information from process memory via a crafted HTML page when the user performs specific UI gestures.

MitigationUpdate Google Chrome to version 150.0.7871.47 or later. Users should avoid engaging with untrusted HTML pages or UI gestures from unknown sources until the browser is updated.

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.46

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

CVSS:3.1/AV:N/AC:H/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. Confirm Google Chrome is installed on Windows
    Check for Chrome in Program Files or by searching for chrome.exe in common paths (e.g., C:\Program Files\Google\Chrome\Application\chrome.exe)
    Affected if Chrome browser is not installed on the system
  2. Determine the installed Chrome version on Windows
    Open Chrome and navigate to chrome://version, or click Menu > Help > About Google Chrome. Alternatively, right-click chrome.exe > Properties > Details to view the File Version
    Affected if Unable to determine the installed version
  3. Compare your Chrome version against the affected range
    If the version shows 150.0.7871.46 or higher (including 150.0.7871.47+), you are NOT affected. If it shows 150.0.7871.45 or lower, you ARE in the affected range
    Affected if Installed version is less than 150.0.7871.46 (e.g., 150.0.7871.45, 150.0.7871.0, 149.x.x.x, etc.)
  4. Verify the platform is Windows
    Confirm the Chrome installation is on a Windows operating system (the vulnerability applies specifically to Windows)
    Affected if Chrome is running on Linux, macOS, or other non-Windows platforms (not affected by this specific CVE)
  5. Assess exposure to user interaction requirements
    The vulnerability requires specific UI gestures with DevTools while visiting untrusted HTML pages. Consider whether users in your environment commonly open DevTools (F12) on untrusted websites
    Affected if Users have access to DevTools and may interact with untrusted web content (the attack vector requires this interaction)

You are affected if Chrome on Windows is installed with a version lower than 150.0.7871.46 and users can open DevTools while viewing untrusted web pages.

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.46 or later
Fixed in 150.0.7871.46
Interim mitigation

Update Google Chrome to version 150.0.7871.47 or later. Users should avoid engaging with untrusted HTML pages or UI gestures from unknown sources until the browser is updated.

Recommended fix High confidence

Chrome 150.0.7871.47 or later

  1. Open Google Chrome on your machine
  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 automatically check for and download the latest version
  6. Wait for the update to download (version 150.0.7871.47 or later)
  7. Click 'Relaunch' or restart Chrome manually to apply the update
  8. Verify the update by returning to Help > About Google Chrome and confirming version 150.0.7871.47 or later is installed

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