dbcve.org
ChromeWeb browser · Google

CVE-2026-13875

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 GPU in Google Chrome on Windows 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

Insufficient input validation in Chrome's GPU component on Windows allows a remote attacker who has already compromised the renderer process to read sensitive data from process memory via a specially crafted HTML page. This is an information disclosure vulnerability stemming from improper validation of untrusted input in the GPU rendering pipeline.

MitigationUpdate Google Chrome to version 150.0.7871.47 or later to patch the vulnerability. Organizations should ensure automated browser update mechanisms are enabled and functioning.

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 Chrome is installed on Windows
    Open Command Prompt or PowerShell and run: reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome" or check C:\Program Files\Google\Chrome\Application\chrome.exe exists
    Affected if Chrome is not installed on the Windows system, this specific vulnerability does not apply
  2. Retrieve installed Chrome version
    Open Chrome, click the three-dot menu > Help > About Google Chrome, or run chrome --version in Command Prompt, or check the Version value in the registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome
    Affected if Unable to determine the installed version - without a version number, the affected status cannot be confirmed
  3. Compare version to affected range
    Compare the installed version number (e.g., 150.0.7871.x) to the vulnerable version range: any version below 150.0.7871.46
    Affected if Installed version is 149.x.x.x or 150.0.7871.45 or lower - the system is running a vulnerable version
  4. Verify Windows platform
    Confirm the operating system is Windows (this vulnerability affects Chrome on Windows only per the CVE description)
    Affected if The system is running Chrome on macOS or Linux - this specific CVE does not affect those platforms

A system is affected if it runs Google Chrome on Windows with version lower than 150.0.7871.46 - the vulnerability requires a compromised renderer process to be exploitable.

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 to patch the vulnerability. Organizations should ensure automated browser update mechanisms are enabled and functioning.

Recommended fix High confidence

Chrome 150.0.7871.47 or later for Windows

  1. Open Google Chrome on Windows
  2. Navigate to Settings (three dots menu) > Help > About Google Chrome
  3. Chrome will automatically check for and download the latest version
  4. Restart Chrome when prompted to complete the update
  5. Verify the version by returning to About Google Chrome - it should show version 150.0.7871.47 or later

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