ChromeWeb browser · Google
CVE-2026-13775
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 · uneditedUse after free in GPU in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Critical)
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 confidenceUse-after-free vulnerability in Chrome's GPU process allowing a remote attacker who has already compromised the renderer process to potentially escape the sandbox and execute code in a privileged context. The flaw exists prior to Chrome version 150.0.7871.47 and is triggered via specially crafted HTML pages.
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
< 150.0.7871.47CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Chrome versionNavigate to chrome://settings/help or look at About Google Chrome in the Chrome menu to see the current version numberAffected if Version is less than 150.0.7871.47 (e.g., 149.x.x.x, 148.x.x.x, etc.)
-
Confirm GPU process is enabledGo to chrome://gpu and look for 'GPU process' status in the 'Graphics' section, or check if 'Use hardware acceleration when available' is enabled in chrome://settingsAffected if GPU process is enabled (this is the default and required condition for exploitation)
-
Verify Chrome is not running in a restricted modeCheck if Chrome is launched with flags like --disable-gpu-sandbox or if running in enterprise-managed mode. Run chrome://version to see active command-line flagsAffected if Browser is running with standard privileges (not heavily sandboxed enterprise mode)
You are affected if your Chrome version is below 150.0.7871.47 and the GPU process is enabled, which is the default configuration.
Generated from the published advisory. Verify against your own configuration.
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 · scoped150.0.7871.47
Update Google Chrome to version 150.0.7871.47 or later. Organizations should prioritize browser patch management and consider enterprise deployment tools to ensure consistent updates across endpoints.
Chrome 150.0.7871.47 or later
- Open Google Chrome and navigate to Settings (three-dot menu in top-right corner)
- Click on 'About Chrome' in the left sidebar menu
- Chrome will automatically check for updates; if an update is available, it will begin downloading
- Once the update is downloaded, click 'Restart' to apply the update
- Verify the version by returning to 'About Chrome' - it should show version 150.0.7871.47 or later
- Alternatively, users can manually download the latest Chrome version from the official Google Chrome website
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
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-13775 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-13775 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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