ChromeWeb browser · Google
CVE-2026-12464
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 Browser in Google Chrome prior to 149.0.7827.155 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 confidenceUse-after-free vulnerability in Google Chrome's browser component (not the renderer) prior to version 149.0.7827.155 allows a remote attacker who has already compromised the renderer process to potentially escape the sandbox via a crafted HTML page, achieving elevated privileges.
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
< 149.0.7827.155CVSS 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 if Google Chrome is installedOpen Chrome, navigate to chrome://version, or run 'google-chrome --version' in terminalAffected if Google Chrome is not installed - not affected
-
Determine the installed Chrome versionNote the full version number displayed (e.g., 149.0.7827.155 or earlier)Affected if Version cannot be determined - further investigation required
-
Compare version against the patched releaseCompare your installed version number to 149.0.7827.155 using semantic version comparisonAffected if Installed version is less than 149.0.7827.155 - potentially affected
-
Verify the attack surface existsConfirm the browser component is in active use (Chrome is running and processing web content)Affected if Chrome is not running or only used for trivial purposes - reduced exposure but version still matters
You are affected if Google Chrome is installed with a version lower than 149.0.7827.155 and the browser is actively used, since the vulnerability allows a compromised renderer process to escape the sandbox.
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 · scoped149.0.7827.155
Update Google Chrome to version 149.0.7827.155 or later to remediate the vulnerability.
Chrome 149.0.7827.155 or later
- 1. Open Google Chrome and navigate to Help > About Google Chrome to check your current version
- 2. If your version is lower than 149.0.7827.155, download the latest stable version of Google Chrome from the official website at https://www.google.com/chrome/
- 3. Run the installer and allow it to update Chrome to the latest version
- 4. Restart Chrome after the update completes
- 5. Verify the version by returning to Help > About Google Chrome and confirm the version is 149.0.7827.155 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
- Implementation2.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-12464 — 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-12464 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