How severe is GHSA-6rvj-pw9w-jcvc?

No CVSS score has been assigned to GHSA-6rvj-pw9w-jcvc yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-6rvj-pw9w-jcvc?

GHSA-6rvj-pw9w-jcvc affects the following packages: onionshare-cli (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-6rvj-pw9w-jcvc?

Update onionshare-cli to 2.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6rvj-pw9w-jcvc is resolved across your whole dependency graph.

How do I detect GHSA-6rvj-pw9w-jcvc in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for onionshare-cli, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-6rvj-pw9w-jcvc if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is GHSA-6rvj-pw9w-jcvc actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-6rvj-pw9w-jcvc, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-6rvj-pw9w-jcvc?

GHSA-6rvj-pw9w-jcvc has an EPSS (Exploit Prediction Scoring System) score of 1.8%, placing it in the 78th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-6rvj-pw9w-jcvc published, and has it been updated?

GHSA-6rvj-pw9w-jcvc was published on November 19, 2021 and was last updated on July 6, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

Information disclosure vulnerability in OnionShareGHSA-6rvj-pw9w-jcvc

GHSA-6rvj-pw9w-jcvc is a security vulnerability in onionshare-cli. 1 public exploit reference exists, so weaponization risk is real. A fix is available for onionshare-cli — see the affected versions and patch details below.

Also known asCVE-2021-41867PYSEC-2026-696

Published

Nov 19, 2021

Updated

Jul 6, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Oct 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs78th percentile — riskier than 78% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐍onionshare-cli

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`onionshare-cli`	≥ 2.3&&< 2.4	2.4`pip install --upgrade 'onionshare-cli==2.4'`

Affected Products

1 product · 1 configurations

Application

onionshareonionshare

≥ 2.3 && < 2.4

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

An information disclosure vulnerability in OnionShare 2.3 before 2.4 all…

ihteam.netNVDOct 2021

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for onionshare-cli, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update onionshare-cli to 2.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6rvj-pw9w-jcvc is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-6rvj-pw9w-jcvc in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works