ChromeWeb browser · Google
CVE-2026-15118
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 Input in Google Chrome prior to 150.0.7871.115 allowed a remote attacker to execute arbitrary code inside a sandbox 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 confidenceA use-after-free vulnerability in the Input component of Google Chrome versions prior to 150.0.7871.115 allows a remote attacker to execute arbitrary code via a crafted HTML page. The vulnerability involves improper memory management where memory is accessed after being freed, leading to potential 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.
-
Locate the Chrome installationOpen Chrome and navigate to chrome://version, or go to Settings > About Chrome. The installed version is displayed at the top of the page.Affected if Chrome is installed on the system
-
Identify the full version numberOn the chrome://version page, note the 'Google Chrome' version string (e.g., 150.0.7871.77). This is the installed version to compare.Affected if Chrome version is displayed and can be compared
-
Compare against the affected version rangeParse the version number and compare it to 150.0.7871.115 using version comparison rules. The major version (150) and subsequent components (0.7871.x) determine if the installed version falls below the threshold.Affected if Installed version is lower than 150.0.7871.115 (e.g., 149.x, 148.x, etc.)
-
Confirm the Input component exposureThis vulnerability affects the Input component. Ensure Chrome is used for browsing or processing HTML content, as the attack vector requires rendering a crafted HTML page.Affected if Chrome is actively used to render untrusted HTML content
A user is affected if the installed Google Chrome version is lower than 150.0.7871.115, placing it within the vulnerable version range.
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
Upgrade Google Chrome to version 150.0.7871.115 or later. Apply browser updates across all affected endpoints and verify successful patch deployment.
Chrome 150.0.7871.115 or later
- 1. Open Google Chrome and navigate to Settings > Help > About Google Chrome
- 2. Chrome will automatically check for updates and display the current version
- 3. If the version is below 150.0.7871.115, click 'Update Google Chrome'
- 4. Restart Chrome after the update completes
- 5. Verify the update by returning to Settings > Help > About Google Chrome and confirming version 150.0.7871.115 or later is installed
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
- Testing2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-15118 — 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-15118 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