Quick answers
- Is CVE-2026-82982 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82982 being exploited in the wild.
- How severe is CVE-2026-82982?
- Medium severity, with a CVSS score of 4.3, published 18 September 2026.
- Which products and versions are affected?
- Nextcloud Approval <UNKNOWN>.
- Is there a fix for CVE-2026-82982?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-82982 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-82982?
- Check whether you run Nextcloud Approval at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an authentication/validation bypass in the approve/reject endpoint of Nextcloud's Approval app. The endpoint is designed to enforce an etag (entity tag) freshness check to ensure the approver is acting on the current version of the file and has reviewed recent changes. However, the backend only validates this check when the etag parameter is present and non-empty; if the parameter is omitted entirely, the check is skipped. An attacker with network access to intercept approval requests can remove the etag field, bypass the freshness check, and approve or reject files without confirming the approver reviewed the current version. No authentication bypass is required if the attacker can intercept an existing request. A patch is expected to enforce the freshness check unconditionally.
Affected products
- Nextcloud Approval <UNKNOWN>
Timeline
- 2026-09-18: disclosed
- advisory: CVE-2026-82982