ChromeWeb browser · Google
CVE-2026-12465
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 · uneditedObject lifecycle issue in Metrics 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 · moderate confidenceObject lifecycle bug in Chrome's Metrics component allows a remote attacker who has already compromised the renderer process to potentially escape the browser sandbox via a crafted HTML page. This is a privilege escalation from within the sandbox to the underlying system.
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.
-
Verify Google Chrome is installedCheck for Chrome installation by looking for chrome.exe in typical installation paths (e.g., C:\Program Files\Google\Chrome\Application\chrome.exe on Windows, /Applications/Google Chrome.app on macOS, or via 'which google-chrome' on Linux)Affected if Chrome is not installed on the system
-
Retrieve the installed Chrome versionOpen Chrome, navigate to chrome://settings/help, or use command line: 'google-chrome --version' on Linux, or check file properties of chrome.exe on WindowsAffected if Unable to determine the version - assume potentially affected if Chrome is present
-
Compare installed version against affected rangeCompare the installed version number to 149.0.7827.155 - versions are affected if they are lower (e.g., 149.0.7827.100, 148.0.5352.88, etc.)Affected if Installed version is less than 149.0.7827.155
-
Check for enterprise-managed updates (optional context)If managed by enterprise policy, verify Chrome update deployment status through group policy or endpoint management consoleAffected if Unable to verify update status - treat as potentially affected
A system is affected if Google Chrome is installed with a version number lower than 149.0.7827.155, as this version addresses the object lifecycle vulnerability in the Metrics 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. In enterprise environments, ensure automated browser patch deployment is configured and verify complete coverage across all managed endpoints.
Chrome version 149.0.7827.155
- 1. Open Google Chrome on the affected system
- 2. Navigate to Chrome Settings (three dots menu > Settings)
- 3. Click on 'About Chrome' in the left sidebar
- 4. Chrome will automatically check for updates and display the current version
- 5. If the version is below 149.0.7827.155, click 'Update Google Chrome'
- 6. Wait for the update to download and install
- 7. Restart Chrome to apply the update
- 8. Verify the version is now 149.0.7827.155 or later by returning to 'About Chrome'
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.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-12465 — 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-12465 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