Skip to content
Fencer Vulns
medium 5.3

CVE-2021-41867 json

Information disclosure vulnerability in OnionShare

published 2021-10-04 5 y ago modified 2026-07-06 4 mo ago also GHSA-6rvj-pw9w-jcvc , PYSEC-2026-696 , EUVD-2021-2310

cvss
5.3
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.8%
EPSS 1.8% chance of exploitation in 30 days, percentile 78%
public exploits
0
none known

Summary

An information disclosure vulnerability in OnionShare 2.3 before 2.4 allows remote unauthenticated attackers to retrieve the full list of participants of a non-public OnionShare node via the --chat feature.

Patch / fix

  • pypi onionshare-cli 2.4
  • onionshare onionshare 2.4
  • onionshare Debian 14, Debian 13, Debian 12 2.5-1

debian advisories DEBIAN-CVE-2021-41867

  • python-onionshare openSUSE Tumbleweed 2.4-1.1
  • python3-onionshare openSUSE Tumbleweed 2.6-4.1

opensuse advisories openSUSE-SU-2024:11557-1openSUSE-SU-2024:13635-1

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-2021-41867 updated cvss 7.5

onionshare: disclosure of chat participants to unauthenticated users when using –chat option in non-public mode

  • Red Hat All currently supported Red Hat products
    not 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

1.81% chance of exploitation in the next 30 days, higher than 78% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • ihteam.net https://www.ihteam.net/advisory/onionshare/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N

Affected packages

ecosystem package affected fixed in
pypi onionshare-cli
>=2.3, <2.4
2.4

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Vulns 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.