CVE-2026-76032: pydio cells · Missing Authorization
Affects pydio cellsSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| pydiocells | Affected
| Fixed in– |
GitHubcellspkg:github/cellsOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until a fix is available, restrict authenticated user roles to limit exposure and monitor access to share-link endpoints. Avoid sharing workspace UUIDs publicly if possible. Follow vendor guidance once an official fix or update is released for Pydio Cells versions 5.0.0 through 5.0.2.
Description
Pydio Cells 5.0.0 through 5.0.2 returns share-link details to any authenticated user. The REST handler for GET /a/share/link/{Uuid} in idm/share/rest/handler.go reads the workspace UUID from the path, calls LinkById, and writes the result with no authorization step, whereas the sibling handler for GET /a/share/cell/{Uuid} loads the workspace and requires MatchPolicies with ResourcePolicyAction_READ, returning a not-found error so that existence is not disclosed. Nothing compensates further down: GetLinkWorkspace reaches GetOrCreateWorkspace, which issues SearchWorkspace with a query carrying no ResourcePolicyQuery, and PrepareResourcePolicyQuery returns the query unmodified when that field is nil, so the workspace service applies no policy filter. The workspace UUID is not secret, because the unauthenticated public page served for a share link embeds it as START_REPOSITORY. Any account holding a standard user role can therefore submit the UUID and receive the link hash and URL, the owner's user identifier, the hidden share user login, the permission set, the download limit and count, the target users, the expiry, and the password-required flag, while a direct read of the shared node from the same account is refused.
References
- github.com/pydio/cells/issues/981 (opens in a new tab)
- github.com/pydio/cells/blob/v5.0.2/idm/share/rest/handler.go (opens in a new tab)
- github.com/pydio/cells/blob/v5.0.2/idm/share/rest/handler.go (opens in a new tab)
- github.com/pydio/cells/blob/v5.0.2/common/proto/service/converter.go (opens in a new tab)
- github.com/pydio/cells/blob/v5.0.2/frontend/web/public-handler.go (opens in a new tab)
- github.com/pydio/cells (opens in a new tab)
- vulncheck.com/advisories/pydio-cells-to-missing-authorization-on-the-share-link-rest-handler (opens in a new tab)