ChromeWeb browser · Google
CVE-2026-7333
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 147.0.7727.138 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)
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 confidenceThis is a use-after-free vulnerability in the GPU (graphics processing unit) component of Google Chrome. A remote attacker can exploit this by tricking users into visiting a specially crafted HTML page, which allows the attacker to potentially escape the browser's sandbox and execute arbitrary code.
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
< 147.0.7727.138CVSS 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.
-
Verify Google Chrome is installedCheck for Chrome installation by looking in typical locations: Windows: C:\Program Files\Google\Chrome\Application\chrome.exe, macOS: /Applications/Google Chrome.app, Linux: /usr/bin/google-chrome or /opt/google/chrome/chromeAffected if Google Chrome browser is present on the system
-
Retrieve the installed Chrome versionOpen Chrome and navigate to chrome://settings/help, or run 'google-chrome --version' from command line on Linux/Mac, or right-click the Chrome shortcut and select Properties on WindowsAffected if The version displayed is lower than 147.0.7727.138
-
Confirm the GPU component is in useThis vulnerability affects the GPU component. To check if GPU rendering is enabled, navigate to chrome://gpu in the browser address bar and look for 'GPU process' statusAffected if GPU hardware acceleration is enabled (this is the default setting)
-
Check for browser profile usageThis use-after-free is triggered by visiting a crafted HTML page. Determine if the browser profile is used for untrusted web contentAffected if Chrome is used for browsing untrusted websites
The environment is affected if Google Chrome is installed with a version lower than 147.0.7727.138 and the browser is used to access web content (which enables GPU component processing).
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 · scoped147.0.7727.138
Update Google Chrome to version 147.0.7727.138 or later to patch this vulnerability.
Chrome 147.0.7727.138 or later
- Open Google Chrome browser
- Click the three-dot menu icon in the top-right corner
- Select 'Settings' from the dropdown menu
- Click 'About Chrome' in the left sidebar
- Chrome will automatically check for and install updates
- Restart the browser if an update was installed
- Verify the version is 147.0.7727.138 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
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7333 — 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-7333 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