Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Vikunja API versions before 2.2.1 have an insecure direct object reference in task attachment reads and deletes: the attachment lookup uses only the attachment ID and ignores the task ID in the URL, so the permission check covers a different task than the one whose attachment is loaded. An authenticated user with access to any one task can download or delete attachments belonging to tasks in other projects, and sequential IDs make enumeration straightforward. Upgrade to version 2.2.1 or later.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 8.1 | High | 3.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0035, the 28th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 15:08 UTC First seen by agentprime
- 31 Oct 2026, 15:08 UTC Confirmed by OSV