ChromeWeb browser · Google
CVE-2026-14037
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 · uneditedInsufficient policy enforcement 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: Low)
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 confidenceInsufficient policy enforcement in the GPU component of Google Chrome prior to version 150.0.7871.47 allows a remote attacker who has already compromised the renderer process to potentially escape the sandbox via a crafted HTML page. This is a privilege escalation bug that requires an already-compromised renderer as a prerequisite.
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
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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://version in the Chrome browser or access Chrome > Help > About Google ChromeAffected if The displayed version is earlier than 150.0.7871.47
-
Verify Chrome version via command lineOn Windows, run 'chrome --version' or check Registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App\Paths\chrome.exe. On macOS, run '/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version'Affected if The version number returned is less than 150.0.7871.47
-
Confirm GPU process is in useOpen chrome://gpu in Chrome and inspect the 'GPU process' status sectionAffected if GPU process is enabled and the Chrome version is below 150.0.7871.47 - the vulnerability exists in the GPU component and requires the renderer to already be compromised as an attack prerequisite
You are affected if your installed Google Chrome version is earlier than 150.0.7871.47 and the GPU component is active, noting this is a secondary escape mechanism requiring a pre-compromised renderer process.
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 to patch the GPU policy enforcement vulnerability.
Chrome 150.0.7871.47 or later
- Open Google Chrome browser
- Click on the three-dot menu icon in the top-right corner
- Select 'Settings' from the dropdown menu
- Scroll down and click 'About Chrome' in the left sidebar
- Chrome will automatically check for updates; if an update is available, click 'Restart' to apply it
- After restarting, verify the version is 150.0.7871.47 or later by returning to About Chrome
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14037 — 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-14037 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