dbcve.org
ChromeWeb browser · Google

CVE-2026-13935

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
Side-channel information leakage in ComputePressure in Google Chrome prior to 150.0.7871.47 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 side-channel information leakage vulnerability in Google Chrome's ComputePressure API (used to monitor system resource usage) allowed a remote attacker to leak cross-origin data by tricking a user into visiting a crafted HTML page. The attack exploits timing differences or pressure state observations to infer information from other origins.

MitigationUpdate Google Chrome to version 150.0.7871.47 or later to patch the ComputePressure side-channel. In enterprise environments, deploy the browser update via centralized patch management and verify compliance.

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
    Locate Chrome executable: On Windows check C:\Program Files\Google\Chrome\Application\chrome.exe or C:\Program Files (x86)\Google\Chrome\Application\chrome.exe; On macOS check /Applications/Google Chrome.app; On Linux check /opt/google/chrome/chrome or /usr/bin/google-chrome
    Affected if Chrome browser is present on the system
  2. Determine installed Chrome version
    Open chrome://version in the Chrome browser address bar, or run 'google-chrome --version' from command line on Linux, or right-click the Chrome executable and select Properties > Details to view File Version
    Affected if Cannot determine version - verification cannot be completed
  3. Compare version against affected range
    Compare the installed version number to the affected range: any version below 150.0.7871.47 is vulnerable. Chrome versions are formatted as major.minor.build.patch (e.g., 149.0.2623.112 is below 150.0.7871.47)
    Affected if Installed version is less than 150.0.7871.47 (e.g., 149.x.x.x, 148.x.x.x, etc.)
  4. Verify ComputePressure API is accessible
    The ComputePressure API is a web API enabled by default in vulnerable Chrome versions. No explicit configuration flag exists to disable it. To test if a specific page can access it, open Developer Tools (F12), go to Console, and run: if (window.computePressure) console.log('API available'); else console.log('API not available')
    Affected if ComputePressure API is available in the browser (this is the default state in vulnerable versions)

The environment is affected if Google Chrome version is below 150.0.7871.47 and the user can browse the web, since the ComputePressure API side-channel can be exploited through any visited crafted HTML page.

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 to patch the ComputePressure side-channel. In enterprise environments, deploy the browser update via centralized patch management and verify compliance.

Recommended fix High confidence

Chrome 150.0.7871.47 or later

  1. Open Chrome and navigate to chrome://settings/help to check the current version
  2. If the version is below 150.0.7871.47, click 'Update Google Chrome' to upgrade to the latest version
  3. Alternatively, wait for Chrome's automatic update to install the patched version
  4. Restart Chrome after the update completes to apply the fix

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