Security readout for executives and security teams
Plain-English summary
Nextcloud Android users using end-to-end encryption could have encrypted files to the wrong public key when adding another encrypted device. If the server provided a malicious public key, affected data could become readable by a malicious actor. The issue is fixed in Android client 3.16.1.
Executive priority
Treat as a targeted confidentiality risk, not a broad service outage risk. Prioritize upgrade for users handling sensitive files through Nextcloud end-to-end encryption, especially where multiple Android devices are enrolled.
Technical view
Before 3.16.1, the Nextcloud Android client skipped verification that a private key matched the previously downloaded public certificate during end-to-end encryption device setup. This is a certificate validation weakness, tracked as CWE-295, with CVSS 3.1 score 5.7 and high confidentiality impact.
Likely exposure
Exposure is limited to Nextcloud Android Client versions before 3.16.1 when the end-to-end encryption feature is used and additional encrypted devices are added to an account.
Exploitation context
The bundle does not show KEV listing or public evidence of active exploitation. Abuse requires a malicious public key being served during device setup and user interaction with end-to-end encrypted device onboarding.
Researcher notes
Evidence supports a device-setup validation flaw rather than a general Nextcloud server compromise. The public bundle names the patch and workaround but does not provide operational indicators, exploitation telemetry, or broader affected platform claims.
Mitigation direction
- Upgrade Nextcloud Android Client to version 3.16.1 or later.
- Until upgraded, do not add additional end-to-end encrypted devices to user accounts.
- Review the Nextcloud advisory for any environment-specific guidance.
- Prioritize users who rely on Nextcloud end-to-end encryption.
Validation and detection
- Inventory Android client versions and identify clients below 3.16.1.
- Confirm whether Nextcloud end-to-end encryption is enabled for affected users.
- Check whether additional encrypted devices were added while using vulnerable clients.
- Verify upgraded clients complete encrypted device setup using the patched version.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-295: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2021-32727 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.7 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N2.13.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.7MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/nextcloud/security-advisories/security/advisories/GHSA-5v33-r9cm-7736CVE reference · x_refsource_CONFIRM
- https://github.com/nextcloud/android/pull/8438CVE reference · x_refsource_MISC
- https://hackerone.com/reports/1189162CVE reference · x_refsource_MISC
- https://github.com/nextcloud/end_to_end_encryption_rfc/blob/7f002996397faefb664019a97ebb0a1e210f64f0/RFC.md#further-devicesCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Certificate Validation
Improper Certificate Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.