The Approval app's approve/reject endpoint is meant to require the file's current etag as a freshness check, preventing an approver from approving or rejecting a file whose contents changed after they reviewed it. The backend only enforced this check when the etag parameter was present and non-empty in the request. An attacker able to intercept and modify the approval request could omit the etag field entirely, bypassing the freshness check and approving or rejecting a file version they never reviewed.
References
| Link | Resource |
|---|---|
| https://hackerone.com/reports/3610332 |
Configurations
No configuration.
History
18 Sep 2026, 02:17
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-09-18 02:17
Updated : 2026-09-18 20:17
NVD link : CVE-2026-82982
Mitre link : CVE-2026-82982
CVE.ORG link : CVE-2026-82982
JSON object : View
Products Affected
No product.
CWE
CWE-840
Business Logic Errors
