CVE-2016-5026 json
hs.py in OnionShare before 0.9.1 allows local users to modify the hiddenservice by pre-creating the /tmp/onionshare directory.
published 2017-01-30 9 y ago modified 2026-06-17 4 mo ago also EUVD-2016-5979
- cvss
- 5.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 25%
- public exploits
- 0
- none known
Summary
hs.py in OnionShare before 0.9.1 allows local users to modify the hiddenservice by pre-creating the /tmp/onionshare directory.
Patch / fix
- onionshare Debian 14, Debian 13, Debian 12 0.8.1-2
debian advisories DEBIAN-CVE-2016-5026
- github.com/micahflee/onionshare advisory
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2016-5026 updated cvss 4.4
onionshare: /tmp usage race condition
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.33% chance of exploitation in the next 30 days, higher than 25% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.5 | CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 2.1 | AV:L/AC:L/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-284 Improper Access Control
References
-
github.com
/micahflee/onionshare
issue-tracking, patch, third-party-advisory
-
openwall.com
/lists/oss-security/2016/05/23/5
mailing-list, third-party-advisory
-
securityfocus.com
/bid/90821
vdb-entry, third-party-advisory
-
openwall.com
/lists/oss-security/2016/05/24/9
mailing-list, third-party-advisory
Sources
- CVE List CVE-2016-5026
- NVD CVE-2016-5026
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.