ChromeWeb browser · Google
CVE-2026-6309
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 Viz in Google Chrome prior to 147.0.7727.101 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 the Viz component of Google Chrome versions prior to 147.0.7727.101. An attacker who has already compromised the renderer process can exploit this memory safety issue via a specially crafted HTML page to potentially escape the Chrome sandbox and execute code in the browser's privileged context.
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.101CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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 versionOpen chrome://version in the Chrome browser address bar, or run 'chrome --version' from command line, or check the application version through the About Chrome menu optionAffected if The displayed version number is lower than 147.0.7727.101 (for example, 147.0.7727.100, 146.x.x.x, or earlier)
-
Confirm Viz component is in useThe Viz component (VizCompositor) is part of Chrome's rendering pipeline and runs by default; no configuration check needed - this is how Chrome works internallyAffected if Chrome is running normally (the Viz component is always active in the browser process)
-
Assess renderer compromise riskReview endpoint detection logs,EDR alerts, or sandbox telemetry for any indicators of renderer process compromise, suspicious extensions, or malicious web content loadingAffected if The renderer process has been compromised or there are signs of browser exploitation attempts
You are affected if your Chrome version is below 147.0.7727.101 AND an attacker has already gained code execution in the renderer process (the vulnerability enables privilege escalation from that compromised state).
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.101
Update Google Chrome to version 147.0.7727.101 or later. Organizations should verify browser versions across endpoints and push updates through their patch management systems.
Chrome 147.0.7727.101 or later
- Open Google Chrome on your system
- Navigate to chrome://settings/help or go to Menu > Help > About Google Chrome
- Chrome will automatically check for available updates
- If version 147.0.7727.101 or later is available, click 'Update Google Chrome' to download and install it
- Restart Chrome completely to apply the update
- Verify the update by returning to chrome://settings/help and confirming the version is 147.0.7727.101 or higher
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
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 locallyCheck whether your project pulls in CVE-2026-6309 — 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-6309 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