Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Vikunja (code.vikunja.io/api) versions before 2.4.0 are vulnerable. A signed-in user can send an update to a kanban bucket that writes a different project view ID onto it, moving the bucket into another user's kanban view and setting the attacker's account as creator. Upgrade to version 2.4.0 or later. No workaround is listed.
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 |
|---|---|---|---|---|
| 5.0 | Medium | 3.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0034, the 27th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:47 UTC First seen by agentprime
- 31 Oct 2026, 14:47 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-569v-q83c-3j3g
- OSV: GHSA-569v-q83c-3j3g
- github.com/go-vikunja/vikunja/security/advisories/GHSA-569v-q83c-3j3g
- github.com/go-vikunja/vikunja/pull/3239
- github.com/go-vikunja/vikunja/commit/b31d606b8879ebe98fbb2ac5d8b3066b86f59868
- github.com/go-vikunja/vikunja
- github.com/go-vikunja/vikunja/releases/tag/v2.4.0