# CVE-2026-82985: Information disclosure in Server

> An attacker can view metadata of files in the album owner's folders by exploiting how shared smart albums use the viewer's folder configuration.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Sep 2026
- **Updated:** 18 Sep 2026
- **Also known as:** BIT-nextcloud-2026-82985, GHSA-fp2m-3769-mjc9

## What is CVE-2026-82985?

CVE-2026-82985 is a medium-severity vulnerability in Nextcloud Server, published on 18 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Photos app's filter-based "smart albums" build their file listing using the search configuration (photosSourceFolders) of the user viewing the album, rather than the album owner's configuration. When an album owner shares a smart album with another user, that user's own folder configuration is used to determine which of the owner's files are searched — allowing them to discover files (name, file ID, and other metadata) in folders the album owner never intended to include in the shared album.

This requires the album owner to have shared a filter-based smart album with the attacker; it does not allow access to arbitrary users' files without such a share.

Weakness: CWE-284 (Improper Access Control)

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

1 open source package ship an affected version, including nextcloud.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `nextcloud` | Bitnami | All versions | 32.0.0 |

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

Upgrade nextcloud to 32.0.0 or later.

## Is CVE-2026-82985 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82985 is a medium-severity vulnerability in Nextcloud Server, published on 18 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-82985 in the wild and no public exploit code.

Affected packages and fixed versions:
- nextcloud (Bitnami): affected all versions; fixed in 32.0.0

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-82985/ (Markdown: https://insights.sbomify.com/CVE-2026-82985/index.md)
```

## Sources

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

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