Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Vikunja (package code.vikunja.io/api) versions before 2.3.0 are vulnerable to privilege escalation through project reparenting. A user with Write access to a shared project can move it under a project they own, which gives them Admin permissions on the moved project. From there they can delete it, remove other users' access, and change sharing settings. Upgrade to version 2.3.0 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.3 | High | 3.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0029, the 22nd percentile, on 15 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
Sources
- GitHub Advisory Database: GHSA-2vq4-854f-5c72
- OSV: GHSA-2vq4-854f-5c72
- github.com/go-vikunja/vikunja/security/advisories/GHSA-2vq4-854f-5c72
- nvd.nist.gov/vuln/detail/CVE-2026-35595
- github.com/go-vikunja/vikunja/pull/2583
- github.com/go-vikunja/vikunja/commit/c03d682f48aff890eeb3c8b41d38226069722827
- github.com/go-vikunja/vikunja
- github.com/go-vikunja/vikunja/releases/tag/v2.3.0