ChromeWeb browser · Google
CVE-2026-7359
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 ANGLE in Google Chrome prior to 147.0.7727.138 allowed a remote attacker who had compromised the renderer process 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 confidenceA use-after-free vulnerability exists in ANGLE (a graphics library used by Chrome for WebGL) that allows a remote attacker who has already compromised the renderer process to potentially escape the sandbox via a specially crafted HTML page.
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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 versionOpen Chrome, click the three-dot menu in the top-right, select 'Help', then 'About Google Chrome'. The version number is displayed on this page.Affected if The displayed version number is less than 147.0.7727.138 (for example, 147.0.7727.137 or any earlier version).
-
Verify Chrome version via command line (Windows)Open Command Prompt and run: chrome --version or locate chrome.exe in Program Files and run chrome.exe --versionAffected if The reported version is less than 147.0.7727.138.
-
Verify Chrome version via command line (macOS)Open Terminal and run: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --versionAffected if The reported version is less than 147.0.7727.138.
-
Verify Chrome version via command line (Linux)Open Terminal and run: google-chrome --version or chromium --version depending on the package nameAffected if The reported version is less than 147.0.7727.138.
You are affected if Google Chrome is installed and the version is below 147.0.7727.138; the ANGLE graphics library vulnerability requires a compromised renderer process but affects any Chrome version below the patched release.
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
Upgrade Google Chrome to version 147.0.7727.138 or later to patch the vulnerability. This is a high-severity issue that should be prioritized given the potential for sandbox escape.
Chrome 147.0.7727.138 or later
- 1. Open Google Chrome
- 2. Click on the three-dot menu in the top-right corner
- 3. Select 'Help' > 'About Google Chrome'
- 4. Chrome will automatically check for and install any available updates
- 5. If the version shown is less than 147.0.7727.138, wait for the update to complete or manually trigger the update
- 6. Restart Chrome after the update is installed
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation6.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7359 — 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-7359 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