# CVE-2015-6789: Use after free in n/a

> Remote attackers can trigger a use-after-free in Chrome's Blink engine via a race condition, causing denial of service or potential code execution.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 14 Dec 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-h35f-7gwh-g2rm, UBUNTU-CVE-2015-6789

## What is CVE-2015-6789?

CVE-2015-6789 is a critical use after free vulnerability in Google Chrome, published on 14 Dec 2015. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Race condition in the MutationObserver implementation in Blink, as used in Google Chrome before 47.0.2526.80, allows remote attackers to cause a denial of service (use-after-free) or possibly have unspecified other impact by leveraging unanticipated object deletion.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2015-6789?

It affects 1 product.


Products: Google Chrome.

## How do I fix CVE-2015-6789?

Upgrade to a fixed version.

## Is CVE-2015-6789 being exploited?

There is no known exploitation of CVE-2015-6789 in the wild and no public exploit code.

## Other vulnerabilities in Google Chrome

- [CVE-2022-4135](https://insights.sbomify.com/CVE-2022-4135/): Google Chromium GPU Heap Buffer Overflow (critical 9.6, exploited in the wild)
- [CVE-2020-16017](https://insights.sbomify.com/CVE-2020-16017/): Google Chrome Use-After-Free (critical 9.6, exploited in the wild)
- [CVE-2020-16010](https://insights.sbomify.com/CVE-2020-16010/): Google Chrome for Android UI Heap Buffer Overflow (critical 9.6, exploited in the wild)
- [CVE-2026-87491](https://insights.sbomify.com/CVE-2026-87491/): Google Chromium V8 Out of Bounds Write (high 8.8, exploited in the wild)
- [CVE-2026-85046](https://insights.sbomify.com/CVE-2026-85046/): Google Chromium V8 Type Confusion (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-6789 and fix it if it is affected.

What it is: CVE-2015-6789 is a critical use after free vulnerability in Google Chrome, published on 14 Dec 2015. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2015-6789 in the wild and no public exploit code.

Affected product: Google Chrome. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2015-6789/ (Markdown: https://insights.sbomify.com/CVE-2015-6789/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2015-6789
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2015-6789
- OSV: https://osv.dev/vulnerability/CVE-2015-6789

---
From sbomify Insights: https://insights.sbomify.com/CVE-2015-6789/
Summaries are generated and may contain mistakes; the official description above is the record.