NIXPKGS-2026-1047
GitHub issue
published 2 months, 1 week ago
Permalink
CVE-2026-35594
6.5 MEDIUM
- CVSS version (CVSS): 3.1
- Attack Vector (AV): Network (N)
- Attack Complexity (AC): Low (L)
- Privileges Required (PR): None (N)
- User Interaction (UI): None (N)
- Scope (S): Unchanged (U)
- Confidentiality (C): Low (L)
- Integrity (I): Low (L)
- Availability (A): None (N)
- Modified Attack Vector (MAV): Network (N)
- Modified Attack Complexity (MAC): Low (L)
- Modified Privileges Required (MPR): None (N)
- Modified User Interaction (MUI): None (N)
- Modified Confidentiality (MC): Low (L)
- Modified Scope (MS): Unchanged (U)
- Modified Integrity (MI): Low (L)
- Modified Availability (MA): None (N)
by @LeSuisse Activity log
- Created suggestion
- @LeSuisse accepted
- @LeSuisse published on GitHub
Vikunja Link Share JWT tokens remain valid for 72 hours after share deletion or permission downgrade
Vikunja is an open-source self-hosted task management platform. Prior to 2.3.0, Vikunja's link share authentication (GetLinkShareFromClaims in pkg/models/link_sharing.go) constructs authorization objects entirely from JWT claims without any server-side database validation. When a project owner deletes a link share or downgrades its permissions, all previously issued JWTs continue to grant the original permission level for up to 72 hours (the default service.jwtttl). This vulnerability is fixed in 2.3.0.
References
-
https://github.com/go-vikunja/vikunja/security/advisories/GHSA-96q5-xm3p-7m84 x_refsource_CONFIRM
-
https://github.com/go-vikunja/vikunja/pull/2581 x_refsource_MISC
Ignored references (1)
-
https://github.com/go-vikunja/vikunja/releases/tag/v2.3.0 x_refsource_MISC
Affected products
vikunja
- ==< 2.3.0
Package maintainers
-
@adamcstephens Adam C. Stephens <happy.plan4249@valkor.net>
-
@leona-ya Leona Maroni <nix@leona.is>