Vulnerability Database · PyPI · Package report

onionshare-cli: vulnerability history, versions and safety

onionshare-cli is a package in the PyPI ecosystem. Vulert records 27 vulnerabilities for it across 11 releases, from Nov 2021 to Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
27 vulnerabilities recorded C1 H3 M10 U13
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
6 in the last 12 months

Most recent disclosure 04 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on onionshare-cli 2.7.0 i

Updated on 23 Oct 2026

Careful: 2.7.0 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Active

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 2.7.0 — affected i
  • Vulnerabilities on record 27 over 4 years · 6 in the last year i
  • Latest disclosure 04 Aug 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 1 i
  • Stars 7,160 i
  • Last release this month i
  • Licence GPL-3.0-or-later i

Version list, release dates, licence and dependants published by PyPI, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for onionshare-cli, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
2.7.0 16 Oct 2026 H1 GPL-3.0-or-later No Details →
2.6.5 28 Jul 2026 H1 non-standard No Details →
2.6.4 09 Jun 2026 H1 non-standard No Details →
2.6.3 25 Feb 2025 M2 U2 non-standard Yes Details →
2.6.1 28 Feb 2024 M2 U2 non-standard Yes Details →
2.6.0 10 Oct 2022 H1 M2 U2 non-standard No Details →
2.5.0 17 Jan 2022 H1 M2 U2 non-standard No Details →
2.3.3 20 Aug 2021 C1 H2 M10 U13 non-standard Yes Details →
2.3.2 02 Jun 2021 C1 H2 M10 U13 non-standard Yes Details →
2.3.1 22 Feb 2021 C1 H2 M10 U13 non-standard Yes Details →
2.3.0 22 Feb 2021 C1 H3 M10 U13 non-standard No Details →

All 11 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 2
  • 2022 19
  • 2026 6

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 6 of the 27 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for onionshare-cli

The 5 most severe of 27 vulnerabilities recorded for this package

Search all 27 in the database →

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About onionshare-cli

Is onionshare-cli safe to use?

Vulert records 27 vulnerabilities for onionshare-cli in PyPI: 1 critical, 3 high, 10 medium and 0 low, plus 13 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is onionshare-cli's Vulert package health score?

Vulert scores onionshare-cli 60/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of onionshare-cli affected?

Yes. 2.7.0, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of onionshare-cli should I use?

2.7.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does onionshare-cli have?

27 vulnerabilities are recorded for onionshare-cli in the PyPI ecosystem: 1 critical, 3 high, 10 medium and 0 low, plus 13 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new onionshare-cli vulnerabilities disclosed?

6 vulnerabilities were recorded for onionshare-cli in the last 12 months, and the oldest entry in this database dates to 19 Nov 2021. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of onionshare-cli are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor onionshare-cli for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the onionshare-cli version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.