# CVE-2016-1586: Use after free in Oxide

> A malicious webview can trigger a use-after-free in Oxide by reusing an incognito context, potentially allowing code execution or bypassing security restrictions.

- **Severity:** Low 1.8 (`CVSS:3.0/AV:L/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 22 Apr 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-3pf3-mgqq-qmjj, UBUNTU-CVE-2016-1586

## What is CVE-2016-1586?

CVE-2016-1586 is a low-severity use after free vulnerability in Ubuntu Oxide, published on 22 Apr 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A malicious webview could install long-lived unload handlers that re-use an incognito BrowserContext that is queued for destruction in versions of Oxide before 1.18.3.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2016-1586?

It affects 1 product.


Products: Oxide Project Oxide.

## How do I fix CVE-2016-1586?

Upgrade to a fixed version.

## Is CVE-2016-1586 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-1586 and fix it if it is affected.

What it is: CVE-2016-1586 is a low-severity use after free vulnerability in Ubuntu Oxide, published on 22 Apr 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2016-1586 in the wild and no public exploit code.

Affected product: Ubuntu Oxide. 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-2016-1586/ (Markdown: https://insights.sbomify.com/CVE-2016-1586/index.md)
```

## Sources

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

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