dbcve.org
ChromeWeb browser · Google

CVE-2026-15112

HIGH · 8.8 CVSS v3.1 Published 2026-07-08
Fix available
A fix is available. Upgrade to 150.0.7871.115 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges 6 weeks old

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 · unedited
Use after free in Ozone 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: Critical)

In the news

Third-party coverage
Trending covered by 1 outlet this week · latest 5d ago

Surfaced from public web coverage — external links open in a new tab.

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 confidence

Use-after-free vulnerability in Chrome's Ozone window management layer (versions prior to 150.0.7871.115) allows remote attackers to corrupt heap memory via malicious HTML pages.

MitigationUpdate Google Chrome to version 150.0.7871.115 or later to patch the vulnerability.

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
Affected:< 150.0.7871.115

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Google Chrome version
    Navigate to chrome://settings/help or use the Chrome menu > Help > About Google Chrome to display the current version number
    Affected if The displayed version is lower than 150.0.7871.115 (for example, 149.x.x.x or earlier)
  2. Verify Chrome version via command line
    On Windows, run 'reg query "HKEY_CURRENT_USER\Software\Google\Chrome\BLBeacon" /v version' or check 'C:\Program Files\Google\Chrome\Application\chrome.exe' properties. On macOS, run 'defaults read /Applications/Google\ Chrome.app/Contents/Info CFBundleVersion'. On Linux, run 'google-chrome --version' or check the package manager
    Affected if The reported version number is less than 150.0.7871.115
  3. Confirm the Ozone platform component presence
    The Ozone platform abstraction layer is an internal Chromium component used on Linux and ChromeOS builds. No user configuration is required - it is included in standard Chrome installations for these platforms
    Affected if Running Chrome on a Linux-based system (including ChromeOS) and the version is below 150.0.7871.115 - the vulnerable component is present by default

You are affected if Google Chrome is installed and the version number is less than 150.0.7871.115, as the vulnerable Ozone platform abstraction layer code is present in all versions below this patch level.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 150.0.7871.115 or later
Fixed in 150.0.7871.115
Interim mitigation

Update Google Chrome to version 150.0.7871.115 or later to patch the vulnerability.

Recommended fix High confidence

Chrome 150.0.7871.115 or later

  1. Open Google Chrome browser
  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'
  7. Restart the browser to complete the installation
  8. Verify the version by returning to 'About Google Chrome' - it should show version 150.0.7871.115 or later

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
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-15112 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-15112 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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