Description
Vikunja is an open-source self-hosted task management platform. Starting in version 0.18.0 and prior to version 2.2.1, when a user account is disabled or locked, the status check is only enforced on the local login and JWT token refresh paths. Three other authentication paths — API tokens, CalDAV basic auth, and OpenID Connect — do not verify user status, allowing disabled or locked users to continue accessing the API and syncing data. Version 2.2.1 patches the issue.
Metrics
CVSS 3.1 8.1/10
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:NWeakness enumeration
Affected software
| Vendor | Product | Versions |
|---|---|---|
| go-vikunja | vikunja | >= 0.18.0, < 2.2.1 |
References
- https://github.com/go-vikunja/vikunja/commit/033922309f492996c928122fb49b691339199c35Patch
- https://github.com/go-vikunja/vikunja/commit/04704e0fde4b027039cf583110cee7afe136fc1bPatch
- https://github.com/go-vikunja/vikunja/commit/0b04768d830c80e9fde1b0962db1499cc652da0ePatch
- https://github.com/go-vikunja/vikunja/commit/fd452b9cb6457fd4f9936527a14c359818f1cca7Patch
- https://github.com/go-vikunja/vikunja/security/advisories/GHSA-94xm-jj8x-3cr4Exploit, Vendor Advisory
- https://vikunja.io/changelog/vikunja-v2.2.2-was-releasedRelease Notes
Timeline
- Published
- Mar 24, 2026
- Last modified
- Jun 17, 2026
- NVD status
- Analyzed