OnionShare follows symlinks in shared directories, allowing unintended disclosure of local files
CVE-2026-54706GHSA-22p9-r2f5-22mf
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (onionshare-cli 2.6.4), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
PyPI onionshare-cli
- Affected
- < 2.6.4
- Fixed in
- 2.6.4
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-22p9-r2f5-22mf lists affected ranges: PyPI onionshare-cli >=0 <2.6.4
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 4.8 · CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:N/A:N
- EPSS
- CVE-2026-54706: 0.34% estimated exploitation activity in the next 30 days; percentile 27.95 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary OnionShare CLI/Desktop 2.6.3 can follow symbolic links inside a selected Share or Website directory and serve the symlink target rather than limiting access to files physically contained in the selected directory. If a user shares a directory that contains attacker-supplied or otherwise untrusted symlinks, a remote recipient with access to the OnionShare service can read arbitrary local files readable by the OnionShare process that the symlink points to. This affects the shipped onionshare-cli Python package and the desktop application because both call the same onionsharecli.web file-indexing and streaming code. Details Tested repository: https://github.com/onionshare/onionshare at commit 8cc75e1d7e88bd31f7276733449d412bf71c8999. Affected product evidence: - cli/pyproject.toml declares onionsharecli version 2.6.3. - desktop/pyproject.toml declares onionshare version 2.6.3 and depends on onionsharecli from ../cli. - cli/setup.py publishes onionshare-cli and includes…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-22p9-r2f5-22mf
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-54706 Advisory: OnionShare follows symlinks in shared directories, allowing unintended disclosure of local files IDs: CVE-2026-54706, GHSA-22p9-r2f5-22mf Record: https://patchnext.com/advisories/cve-2026-54706 (revision 1, source checked 26 Oct 2026, 13:50 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 4.8) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: onionshare-cli 2.6.4. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI onionshare-cli: affected < 2.6.4; fixed in 2.6.4 ## Suggested inspection (read-only) - `python -m pip show onionshare-cli`: prints the installed version. Run with the environment that serves production active. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on onionshare-cli. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-22p9-r2f5-22mf (GitHub-reviewed advisory GHSA-22p9-r2f5-22mf lists affected ranges: PyPI onionshare-cli >=0 <2.6.4) Commands are suggestions: review each one before running it.
Loading voting…