ChromeWeb browser · Google
CVE-2026-15123
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 · uneditedInappropriate implementation in DOM in Google Chrome prior to 150.0.7871.115 allowed a remote attacker 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 confidenceInappropriate implementation in Google Chrome's DOM handling prior to version 150.0.7871.115 allows a remote attacker to trigger heap corruption via a maliciously crafted HTML page, potentially enabling arbitrary 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
ChromeWeb browser
< 150.0.7871.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
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/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.
-
Check installed Chrome versionOpen Chrome and navigate to chrome://version, or go to Help > About Google Chrome. Note the version number displayed.Affected if The installed version is lower than 150.0.7871.115 (e.g., 149.x, 148.x, etc.)
-
Verify Chrome is actively usedConfirm the browser is being used to access web pages, as the vulnerability triggers when processing HTML content.Affected if Users browse the web with an affected Chrome version, allowing malicious HTML pages to be loaded and processed.
-
Check for multiple Chrome installationsOn Windows, check Program Files and Program Files (x86) for multiple Chrome folders. On Mac, check /Applications for Chrome.app. On Linux, run 'which google-chrome' to locate installations.Affected if Multiple Chrome installations exist and any of them are running an affected version.
You are affected if the installed Chrome version is less than 150.0.7871.115 and users browse web pages with that browser.
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 · scoped150.0.7871.115
Update Google Chrome to version 150.0.7871.115 or later. Organizations should ensure endpoints are running current browser versions through standard patch management processes.
Chrome version 150.0.7871.115 or later
- Open Google Chrome and navigate to Settings > About Chrome (or enter chrome://settings/help in the address bar)
- Chrome will automatically check for updates; if version 150.0.7871.115 or later is available, click 'Update Google Chrome'
- Restart the browser to complete the installation of the security update
- Alternatively, on Windows or macOS, ensure Chrome is set to auto-update or manually trigger an update through the browser's menu
- On Linux systems, use the system package manager (e.g., sudo apt-get update && sudo apt-get upgrade google-chrome-stable) to install the patched version
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-15123 — 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-15123 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