ChromeWeb browser · Google

CVE-2026-15765

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

NVD · unedited

Use after free in Ozone in Google Chrome 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

covered by 2 outlets this week · latest 1mo ago

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

Technical summary

dbcve analysis · high confidence

A use-after-free vulnerability exists in the Ozone window management layer of Google Chrome (used primarily on Linux and Chrome OS) before version 150.0.7871.125. An attacker can exploit this by tricking users into performing specific UI gestures while visiting a crafted HTML page, leading to heap corruption and potential arbitrary code execution.

MitigationUpdate Google Chrome to version 150.0.7871.125 or later. Until the update is applied, restrict user access to untrusted HTML content and monitor for unusual browser behavior.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

ChromeWeb browser

Affected:< 150.0.7871.125

CVSS breakdown

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?

dbcve checks

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

Check installed Chrome version

Navigate to chrome://settings/help or run 'google-chrome --version' in terminal

Affected if Version is lower than 150.0.7871.125
Confirm operating system

Run 'uname -a' or check system settings

Affected if Running Linux or Chrome OS (the Ozone layer is not used on Windows/macOS)
Identify browser usage patterns

Survey or interview users about web browsing habits, particularly access to untrusted HTML pages

Affected if Users routinely visit untrusted or malicious websites
Check for crash reports

Review Chrome crash reports in ~/.config/google-chrome/Crashpad/reports or system crash logs

Affected if Unexpected browser crashes with heap corruption signatures are observed
Review security logs

Check browser and system logs for indicators of exploitation attempts or unusual heap activity

Affected if Logs show unusual heap corruption or memory safety events related to Chrome

A user is affected if they run Google Chrome version below 150.0.7871.125 on Linux or Chrome OS and can access untrusted HTML content.

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

Remediation

dbcve · scoped

Upgrade available Upgrade to 150.0.7871.125 or later

Fixed in 150.0.7871.125

Interim mitigation

Update Google Chrome to version 150.0.7871.125 or later. Until the update is applied, restrict user access to untrusted HTML content and monitor for unusual browser behavior.

Recommended fix High confidence

Chrome 150.0.7871.125

Open Google Chrome browser
Click the three-dot menu icon in the top-right corner
Select 'Settings' from the dropdown menu
Scroll down and click 'About Chrome' in the left sidebar
Chrome will automatically check for updates; if an update is available, click 'Update Google Chrome'
Restart the browser to complete the update
Verify the version by returning to 'About Chrome' - it should show version 150.0.7871.125 or later

Caveat No significant breaking changes expected; Chrome updates are typically backward-compatible

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

Fix this in Chrome Scoped from the published advisory

Consultation2.0 h
Implementation3.0 h
Testing2.0 h
Review / QA1.0 h

8.0 hours of engineering $1,420

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,272.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

chromereleases.googleblog.comRelease NotesVendor Advisory
issues.chromium.orgPermissions Required
nvd.nist.govNVD record

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2026-15765?

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.

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

At a glance

A fix existsUpgrade to 150.0.7871.125 or later

Severity 7.5 High

Exploit likelihood EPSS, next 30 days 0.5%

Affects: Chrome

Remediation

A high-priority fix

Fix this in Chrome 8 hrs · Low

Typical engagement from $1,420

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2026-15765 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

In the news

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References