Read the docs

Public shares stay accessible after the owner's account is disabled

Priority LOW 39CWE-284Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
Security bypass
Confidentiality · integrity · availability
Low · None · None
Fix status
Fixed

Attack profile from CVSS 3.1 · GHSA-6m4h-j3wr-v388. Fix status from GitHub. Impact type from CWE-284.

Summary

Nextcloud Server and Nextcloud Enterprise Server have an improper access control flaw (CWE-284). When a user account is disabled, its public shares are revoked at the /s/{token} endpoint but remain reachable through alternate public endpoints. A remote attacker who holds a share token can keep reading files and, for editable shares, modifying content after the owner's account is disabled, without authentication.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

Description from the GitHub advisory

### Impact When a Nextcloud user account is disabled, their public shares are correctly revoked at the primary /s/{token} endpoint but remain accessible through alternate public endpoints. This allows external recipients who possess the share token to continue reading files and, for editable shares, modifying content even after the share owner's account has been disabled. ### Patches It is recommended that the Nextcloud Server is upgraded to 32.0.13 or 33.0.7 or 34.0.2 It is recommended that the Nextcloud Enterprise Server is upgraded to 30.0.17.12 or 31.0.14.8 or 32.0.13 or 33.0.7 or 34.0.2 ### Workarounds <!-- Remove not applicable sections --> * Delete disabled users ### References <!-- Link to the main/master PR only --> * [HackerOne](https://hackerone.com/reports/3620539) * [PullRequest](https://github.com/nextcloud/server/pull/62092) ### For more information If you have any questions or comments about this advisory: * Create a post in [nextcloud/security-advisories](https://github.com/nextcloud/security-advisories/discussions) * Customers: Open a support ticket at [portal.nextcloud.com](https://portal.nextcloud.com)

Why it matters now

Fix Fixed Server (nextcloud): 32.0.13, 33.0.7, 34.0.2Server (nextcloud enterprise): 30.0.17.12, 31.0.14.8, 32.0.13 +2

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
—Server (nextcloud)>= 32.0.0, >= 33.0.0, => 34.0.032.0.13, 33.0.7, 34.0.2Patch availableGHSA-6m4h-j3wr-v388
—Server (nextcloud enterprise)>= 30.0.0, >= 31.0.0, >= 32.0.0, >= 33.0.0, => 34.0.030.0.17.12, 31.0.14.8, 32.0.13, 33.0.7, 34.0.2Patch availableGHSA-6m4h-j3wr-v388
  • Server (nextcloud) Vendor— Affected >= 32.0.0, >= 33.0.0, => 34.0.0 Fixed in 32.0.13, 33.0.7, 34.0.2 Patch available GHSA-6m4h-j3wr-v388
  • Server (nextcloud enterprise) Vendor— Affected >= 30.0.0, >= 31.0.0, >= 32.0.0, >= 33.0.0, => 34.0.0 Fixed in 30.0.17.12, 31.0.14.8, 32.0.13, 33.0.7, 34.0.2 Patch available GHSA-6m4h-j3wr-v388

Remediation

Upgrade Nextcloud Server to 32.0.13, 33.0.7 or 34.0.2, and Nextcloud Enterprise Server to 30.0.17.12, 31.0.14.8, 32.0.13, 33.0.7 or 34.0.2. Until the upgrade, the source suggests deleting disabled users.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

  • Fix · GHSA-6m4h-j3wr-v388 Server (nextcloud) Fixed in 32.0.13, 33.0.7, 34.0.2 Advisory →
  • Fix · GHSA-6m4h-j3wr-v388 Server (nextcloud enterprise) Fixed in 30.0.17.12, 31.0.14.8, 32.0.13, 33.0.7, 34.0.2 Advisory →

Timeline

  1. 2026-11-12 Threatist record created from GHSA-6m4h-j3wr-v388
  2. 2026-11-12 Alias added: CVE-2026-114601

References

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences