# CVE-2026-82983: The Tables app's share-listing endpoint (GET /apps/tables/share/table/{tableId}) did not verify that the requesting user has manage-level pe


- **Severity:** Low 3.3 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Oct 2026
- **Updated:** 27 Oct 2026

## What is CVE-2026-82983?

CVE-2026-82983 is a low-severity vulnerability in Nextcloud Tables, published on 27 Oct 2026. 

### Official description

The Tables app's share-listing endpoint (GET /apps/tables/share/table/{tableId}) did not verify that the requesting user has manage-level permission on the table before returning the full list of share recipients (users, groups, and teams) along with their permission levels. A user who was only granted read-data access to a table, and who is correctly prevented from seeing this information in the web UI, could call the endpoint directly to enumerate everyone the table is shared with and their access levels.

This does not expose the table's data itself beyond what the read-data grant already permits, only the list of share recipients and their permission levels.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-82983 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82983 is a low-severity vulnerability in Nextcloud Tables, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-82983 in the wild and no public exploit code.

Affected product: Nextcloud Tables. 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-82983/ (Markdown: https://insights.sbomify.com/CVE-2026-82983/index.md)
```

## Sources

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

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