CVE-2021-22905 json
Nextcloud Android App (com.nextcloud.client) before v3.16.0 is vulnerable to information disclosure due to searches for sharees being perfo…
published 2021-06-11 5 y ago modified 2026-09-08 2 mo ago also BIT-nextcloud-2021-22905 , EUVD-2021-10034 , GHSA-22v9-q3r6-x7cj
- cvss
- 6.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.4%
- EPSS 1.4% chance of exploitation in 30 days, percentile 72%
- public exploits
- 0
- none known
Summary
Nextcloud Android App (com.nextcloud.client) before v3.16.0 is vulnerable to information disclosure due to searches for sharees being performed by default on the lookup server instead of only using the local Nextcloud server unless a global search has been explicitly chosen by the user.
Patch / fix
- bitnami nextcloud 3.16.0
- nextcloud nextcloud 3.16.0
Exploit prediction
1.37% chance of exploitation in the next 30 days, higher than 72% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- hackerone.com https://hackerone.com/reports/1167916 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:P/I:N/A:N |
| OSV | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | nextcloud | <3.16.0 |
3.16.0 |
Affected products
- n/a Nextcloud Android App (com.nextcloud.client)
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
hackerone.com
/reports/1167916
exploit, issue-tracking, third-party-advisory, advisory
-
github.com
/nextcloud/security-advisories/security/advisories/GHSA-22v9-q3r6-x7cj
third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2021-22905
web
Sources
- CVE List CVE-2021-22905
- NVD CVE-2021-22905
- OSV BIT-nextcloud-2021-22905
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.