ChromeWeb browser · Google
CVE-2026-12008
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 DigitalCredentials in Google Chrome prior to 149.0.7827.115 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Critical)
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 DigitalCredentials component prior to version 149.0.7827.115 allows a remote attacker with a compromised renderer process to potentially escape the sandbox via a 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
< 149.0.7827.115CVSS 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 and look at the first line showing the version number, or run 'chrome --version' from command lineAffected if The installed version is earlier than 149.0.7827.115 (for example, 149.0.7827.100 or any version below 149.0.7827.115)
-
Verify DigitalCredentials component presenceThe DigitalCredentials component is built into Chrome and cannot be separately enabled or disabled; its presence is assumed for all affected Chrome versionsAffected if The Chrome version is below 149.0.7827.115, meaning the vulnerable DigitalCredentials component code is present
-
Assess renderer process compromise riskReview any indicators of compromise or unusual behavior in browser sessions; this vulnerability requires a compromised renderer process to be exploitedAffected if The browser environment has a compromised renderer process AND Chrome version is below 149.0.7827.115
You are affected if Chrome version is below 149.0.7827.115 and an attacker has compromised a renderer process, which can be exploited via a crafted HTML page.
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.115
Update Google Chrome to version 149.0.7827.115 or later; in enterprise environments, deploy the update through centralized patch management and verify compatibility with internal applications.
Chrome 149.0.7827.115 or later
- Open Google Chrome browser
- Click the three-dot menu icon in the top-right corner
- Select 'Help' from the dropdown menu
- Click 'About Google Chrome'
- Chrome will automatically check for updates and download version 149.0.7827.115 or later
- Click 'Relaunch' to restart Chrome and apply the update
- Verify the update by returning to Help > About Google Chrome and confirming the version is 149.0.7827.115 or higher
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-12008 — 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-12008 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