# CVE-2026-45285: Nextcloud: Hidden Public Link creation when sharing to a Team External Member

> Hidden public links created for external team members allow unauthorized access to shared folders without owner visibility or consent.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 1 Jun 2026
- **Updated:** 2 Jun 2026
- **Also known as:** GHSA-r3xh-x86g-hw4m

## What is CVE-2026-45285?

CVE-2026-45285 is a medium-severity missing authorization vulnerability in Nextcloud Nextcloud Server, published on 1 Jun 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Nextcloud is an open source content collaboration platform. From versions 32.0.0 to before 32.0.9, and 33.0.0 to before 33.0.3, when a user shares a folder or file with a Nextcloud Team that includes an external member (a person added via email address who does not have a Nextcloud account), the system automatically creates a public link for that external member. This public link is not displayed in the share section of the folder, so the folder owner has no knowledge of its existence. It is sent via email to the external member. It grants the same permissions (read, write, delete, reshare, download) as the Team’s access. An attacker who receives or intercepts this link can access, modify, delete, reshare, and download all data in the shared folder without any further authentication. The folder owner cannot see or revoke the link through the normal sharing interface. This issue has been patched in versions 32.0.9 and 33.0.3.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-45285?

It affects 1 product.


Products: Nextcloud Nextcloud Server.

## How do I fix CVE-2026-45285?

No fix has been published for CVE-2026-45285 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-45285 being exploited?

There is no known exploitation of CVE-2026-45285 in the wild and no public exploit code.

## Other vulnerabilities in Nextcloud Nextcloud Server

- [CVE-2021-32802](https://insights.sbomify.com/CVE-2021-32802/): Preview generation used third-party library not suited for user-generated content in Nextcloud server (critical 9.3)
- [CVE-2023-26482](https://insights.sbomify.com/CVE-2023-26482/): Scope of workflow operations is not validated in nextcloud server (critical 9.1)
- [CVE-2018-3775](https://insights.sbomify.com/CVE-2018-3775/): Auth bypass in Nextcloud Server (high 8.8)
- [CVE-2023-35172](https://insights.sbomify.com/CVE-2023-35172/): Nextcloud Server password reset endpoint is not brute force protected (high 8.7)
- [CVE-2023-32320](https://insights.sbomify.com/CVE-2023-32320/): Nextcloud Server's brute force protection allows someone to send more requests than intended (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-45285 and fix it if it is affected.

What it is: CVE-2026-45285 is a medium-severity missing authorization vulnerability in Nextcloud Nextcloud Server, published on 1 Jun 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-45285 in the wild and no public exploit code.

Affected product: Nextcloud Nextcloud Server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-45285/ (Markdown: https://insights.sbomify.com/CVE-2026-45285/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-45285
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-45285
- OSV: https://osv.dev/vulnerability/CVE-2026-45285

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-45285/
Summaries are generated and may contain mistakes; the official description above is the record.