dbcve.org
ChromeWeb browser · Google

CVE-2026-15764

HIGH · 7.5 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 150.0.7871.125 or later.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges 5 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 on Linux prior to 150.0.7871.125 allowed a remote attacker who convinced a user to engage in specific UI gestures to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Critical)

In the news

Third-party coverage
Trending covered by 2 outlets this week · latest 1mo 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 · moderate confidence

Use-after-free vulnerability in Google's Ozone platform layer on Linux Chrome allows remote attackers to corrupt heap memory through specific UI gesture interactions, potentially enabling arbitrary code execution via malicious HTML pages.

MitigationUpdate Google Chrome for Linux to version 150.0.7871.125 or later; until patched, avoid interacting with untrusted HTML content and restrict browser usage in high-risk environments.

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.125

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
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/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 if Google Chrome is installed on Linux
    Run 'google-chrome --version' or 'chrome --version' in terminal, or check /usr/bin/google-chrome exists
    Affected if Google Chrome browser is installed on the Linux system
  2. Verify the installed Chrome version number
    Execute 'google-chrome --version' to get the exact version string (e.g., 150.0.7871.0 or 149.0.1234.56)
    Affected if The version shown is lower than 150.0.7871.125 (the version is displayed as three dot-separated numbers)
  3. Confirm Chrome is running on Linux with Ozone platform layer
    Navigate to chrome://version in the browser and check the 'Command Line' or 'Platform' field; all modern Chrome on Linux uses the Ozone platform layer by default
    Affected if Chrome is running on a Linux kernel with the Ozone platform layer enabled (default for Chrome on Linux)
  4. Check for UI gesture handling components
    This vulnerability requires specific UI gesture interactions; no manual config check is needed - the flaw exists in the UI gesture handling code within the Ozone layer
    Affected if The browser processes any UI gestures through the Ozone platform layer (standard operation on Linux Chrome)

A user is affected if they run Google Chrome on Linux with a version lower than 150.0.7871.125, as the use-after-free vulnerability in the Ozone platform layer UI gesture handling can be triggered by malicious HTML pages.

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.125 or later
Fixed in 150.0.7871.125
Interim mitigation

Update Google Chrome for Linux to version 150.0.7871.125 or later; until patched, avoid interacting with untrusted HTML content and restrict browser usage in high-risk environments.

Recommended fix High confidence

Chrome 150.0.7871.125 or later

  1. Ensure Google Chrome is not currently running
  2. Verify the current Chrome version by navigating to chrome://settings/help
  3. Download Chrome version 150.0.7871.125 or later from the official Chrome download page (google.com/chrome)
  4. Install the updated Chrome version
  5. Restart Chrome to complete the update
  6. Verify the version has been updated to 150.0.7871.125 or later via chrome://settings/help
Caveat Minimal risk; Chrome auto-updates typically have no breaking changes for end users

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-15764 — 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-15764 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