Improper access control in Nextcloud Server exposes team resource metadata

Note: This data is for reference and cybersecurity research purposes only.CyStack advises users not to use this information for unlawful purposes.

What is CVE-2026-82984?

CVE-2026-82984 is a vulnerability classified as Improper Access Control, affecting Server (affected versions: 32.0.0 – ≤ 33.0.0). This vulnerability is rated Medium, with a CVSS score of 4.3. There is not enough data to determine whether this vulnerability has been exploited.

Overview

Original source data

When a team was configured as "visible to everyone", the web UI correctly blocked non-members from viewing the team ("You are not a member of..."), but the resources API endpoint could still be called directly, allowing any authenticated non-member to enumerate the team's internal resources and their identifiers. This does not grant access to the contents of the discovered resources themselves, only their existence, names, and identifiers.

Affected products and scope

  • Nextcloud Server: the CNA record identifies 32.0.0 through and including 33.0.0 as affected under semver.
  • The recorded default status is unaffected, while the explicitly listed affected range is the version boundary supported by the record.
  • No additional release branch or more precise fixed boundary is provided in the available evidence.

Technical details

Nextcloud Server correctly applies a membership check in the web UI when a team is configured as “visible to everyone”, but the same authorization boundary is not enforced consistently by the resources API endpoint. An authenticated user who is not a team member can call the endpoint directly and enumerate the team’s internal resources, including their names and identifiers. This is CWE-284, caused by inconsistent access control between the web interface and the API. The required condition is a team configured as “visible to everyone”; the record does not require interaction from another user. The exact endpoint path and request parameters are not disclosed in the available record, so those implementation details remain unknown. The disclosed data is limited to resource existence, names, and identifiers, not the contents of the resources.

Exploitability

The issue is reachable over the network through the resources API endpoint. An attacker needs an authenticated account that is not a member of the target team, and the record describes direct API access without interaction from another user. The target team must be configured as “visible to everyone”. The supplied record does not establish observed exploitation or a public exploit; public detail about exploitation status is limited.

Technical impact

  • The technical result is limited information disclosure: an attacker can determine the existence, names, and identifiers of team resources.
  • The attacker does not gain the ability to read the contents of those resources, and the record does not indicate modification or deletion capability.
  • The impact remains within the same system, affecting confidentiality of resource metadata rather than integrity or availability.
  • Organisational consequences may include disclosure of internal structure or naming conventions. The practical sensitivity depends on what the organization encodes in resource names and identifiers.

Business impact

  • A user outside the team can learn which internal resources exist and obtain their names and identifiers.
  • This can disclose aspects of internal collaboration structure and may support further reconnaissance, although that possible follow-on use is not confirmed by the record.
  • The described issue does not provide access to resource contents, data modification, or service disruption.
  • Organizations should prioritize teams whose resource names or identifiers themselves contain sensitive information, even though the underlying content is not exposed.

Remediation

  1. Identify Nextcloud Server deployments in the 32.0.0 through 33.0.0 affected range and apply the available vendor security update through the normal update channel.
  2. The record indicates that a patch is available but does not name an exact fixed release or provide solution text. Do not infer that every later version is safe without verifying the fixed boundary for each release branch.
  3. Until patching is complete, review teams configured as “visible to everyone” and consider restricting that setting as a temporary risk-reduction measure where operationally acceptable.
  4. After updating, verify the deployment inventory and perform an authorization test with an authenticated account that is not a member of the team to confirm that the API no longer enumerates internal resources.

Detection

  • Inventory Nextcloud Server deployments and compare their versions with the affected range in the record.
  • Identify teams configured as “visible to everyone”, because this is the required condition described for the flaw.
  • If request logging is available, review requests to the resources API endpoint from accounts that are not team members and responses that enumerate resource names or identifiers.
  • Use an authenticated test account that is not a team member to verify that the API no longer returns the team’s internal resource list. This is an authorization validation check, not evidence that similar requests were previously exploited.
  • Do not treat the absence of matching logs as proof of safety; logging may be incomplete or may not retain response contents.
Sources (14)
Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.