dbcve.org
ChromeWeb browser · Google

CVE-2026-13950

MEDIUM · 5.3 CVSS v3.1 Published 2026-06-30
Fix available
A fix is available. Upgrade to 150.0.7871.47 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
Uninitialized Use in GPU in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who had compromised the renderer process 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 · high confidence

This is an uninitialized memory use vulnerability in the GPU component of Google Chrome. A remote attacker who has already compromised the renderer process can exploit this by tricking users into visiting a crafted HTML page, causing the GPU to read and expose uninitialized memory contents back to the attacker, potentially revealing sensitive process memory.

MitigationUpgrade Google Chrome to version 150.0.7871.47 or later to patch the uninitialized use vulnerability in the GPU component.

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
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. Verify Chrome is installed
    Check for Google Chrome installation - on Windows look in Program Files/Google/Chrome/Application/, on macOS check /Applications/Google Chrome.app/, or on Linux check /opt/google/chrome/ or via package manager
    Affected if Google Chrome is installed on the system
  2. Determine installed Chrome version
    Open Chrome, navigate to chrome://settings/help, or run 'google-chrome --version' on Linux, 'C:\Program Files\Google\Chrome\Application\chrome.exe --version' on Windows, or 'Info.plist' inspection on macOS
    Affected if Version is displayed as less than 150.0.7871.47
  3. Compare version to affected range
    Compare the installed version number to the affected range: any version before 150.0.7871.47 is vulnerable
    Affected if Installed version is less than 150.0.7871.47 (e.g., 150.0.7871.0, 149.x.x.x, 148.x.x.x, etc.)
  4. Confirm GPU rendering is active
    In Chrome, go to chrome://settings/system and check if 'Use hardware acceleration when available' is enabled, or inspect running Chrome processes for GPU-related activity
    Affected if Hardware acceleration or GPU rendering is enabled and Chrome is actively used - this is the attack surface for the vulnerability

User is affected if Google Chrome is installed with a version number lower than 150.0.7871.47 and the GPU/hardware acceleration feature is enabled.

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

Upgrade Google Chrome to version 150.0.7871.47 or later to patch the uninitialized use vulnerability in the GPU component.

Recommended fix High confidence

Chrome 150.0.7871.47 or later stable release

  1. Open Google Chrome
  2. Navigate to Chrome Menu > Help > About Google Chrome
  3. Verify the current version number
  4. If the version is lower than 150.0.7871.47, Chrome will automatically check for and install updates
  5. Wait for the update to complete and restart the browser when prompted
  6. After restart, verify the version is 150.0.7871.47 or higher via Help > About Google Chrome
Caveat Routine security update with minimal risk; standard Chrome stable channel update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-13950 — 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-13950 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