CVE-2026-12455
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 Tab Strip in Google Chrome prior to 149.0.7827.155 allowed a remote attacker who convinced a user to engage in specific UI gestures to potentially exploit heap corruption 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 Tab Strip component of Google Chrome. A remote attacker could exploit this by tricking users into performing specific UI gestures on a crafted HTML page, causing the browser to access freed memory and potentially achieve heap corruption and code execution.
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< 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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.
-
Determine Chrome browser versionOpen Chrome, click the three-dot menu (top right), select Help, then select About Google Chrome. The version number is displayed on this page.Affected if Unable to determine version or version shows as Chrome (not a Chromium-based fork like Edge or Brave)
-
Compare against affected versionIf Chrome is confirmed, compare the installed version number to 149.0.7827.155. The first three number groups (149.0.7827) are the major.minor.patch. Check if your version is less than this threshold.Affected if Installed version is less than 149.0.7827.155 (for example, 149.0.7827.100 or 148.x.x.x)
-
Verify exact version matchIn About Google Chrome, confirm the full version string (e.g., 149.0.7827.155). Note that versions like 149.0.7827.154 or earlier are affected, while 149.0.7827.155 and later are patched.Affected if Version ends in .154 or lower, or begins with a number less than 149
If Chrome is the installed browser and the version number is less than 149.0.7827.155, the environment is vulnerable to this use-after-free flaw in the Tab Strip component.
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 patch this vulnerability. Users should refrain from interacting with untrusted HTML pages until the browser is updated.
Google Chrome 149.0.7827.155 or later
- 1. Open Google Chrome browser on your device
- 2. Click the three-dot menu icon in the top-right corner
- 3. Select 'Help' from the dropdown menu
- 4. Click 'About Google Chrome'
- 5. Chrome will automatically check for updates and display the current version
- 6. If an update is available, click 'Update Google Chrome' to download and install it
- 7. After the update installs, click 'Relaunch' to restart the browser
- 8. Once restarted, return to 'About Google Chrome' to confirm the version is 149.0.7827.155 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.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-12455 — 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-12455 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