# CVE-2016-5026: Race condition in n/a

> Local attackers can modify OnionShare hidden services by pre-creating the temporary directory, leading to potential privilege escalation or data modification.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Jan 2017
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2016-5026, GHSA-55hg-465f-gp62, UBUNTU-CVE-2016-5026

## What is CVE-2016-5026?

CVE-2016-5026 is a medium-severity vulnerability in n/a, published on 30 Jan 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

hs.py in OnionShare before 0.9.1 allows local users to modify the hiddenservice by pre-creating the /tmp/onionshare directory.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Onionshare Onionshare.

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

Upgrade to a fixed version.

## Is CVE-2016-5026 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-41868](https://insights.sbomify.com/CVE-2021-41868/): Remote unauthenticated attackers able to upload files in Onionshare (critical 9.8)
- [CVE-2022-21690](https://insights.sbomify.com/CVE-2022-21690/): Cross-Site Scripting in Onionshare (high 8.7)
- [CVE-2022-21688](https://insights.sbomify.com/CVE-2022-21688/): Out-of-bounds Read in Onionshare (high 7.5)
- [CVE-2022-21689](https://insights.sbomify.com/CVE-2022-21689/): Denial of Service in Onionshare (high 7.5)
- [CVE-2018-19960](https://insights.sbomify.com/CVE-2018-19960/): Path traversal in n/a (high 7.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-5026 is a medium-severity vulnerability in n/a, published on 30 Jan 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-5026 in the wild and no public exploit code.

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

## Sources

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

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