Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Vikunja versions before 2.3.0 are affected. Link share JWT tokens are checked only against their claims, with no database lookup, so after a link share is deleted or its permissions are lowered, existing tokens keep the original permission level for up to 72 hours by default. An attacker holding a leaked share link can read, write, or administer the single project it covers until the token expires. Upgrade to Vikunja 2.3.0 or later. The source gives no workaround other than upgrading.
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 |
|---|---|---|---|---|
| 6.5 | Medium | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0032, the 25th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 15:05 UTC First seen by agentprime
- 31 Oct 2026, 15:05 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-96q5-xm3p-7m84
- OSV: GHSA-96q5-xm3p-7m84
- github.com/go-vikunja/vikunja/security/advisories/GHSA-96q5-xm3p-7m84
- nvd.nist.gov/vuln/detail/CVE-2026-35594
- github.com/go-vikunja/vikunja/pull/2581
- github.com/go-vikunja/vikunja/commit/379d8a5c19334ffe4846003f590e202c31a75479
- github.com/go-vikunja/vikunja
- github.com/go-vikunja/vikunja/releases/tag/v2.3.0