CVE-2026-33668
Vikunja Allows Disabled/Locked User Accounts to Authenticate via API Tokens, CalDAV, and OpenID Connect
CVSS Score
0.0
EPSS Score
0.1%
EPSS Percentile
32th
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.
| CWE | CWE-285 CWE-863 |
| Vendor | go-vikunja |
| Product | vikunja |
| Published | Mar 24, 2026 |
| Last Updated | Mar 26, 2026 |
Stay Ahead of the Next One
Get instant alerts for go-vikunja vikunja
Be the first to know when new unknown vulnerabilities affecting go-vikunja vikunja are published — delivered to Slack, Telegram or Discord.
Get Free Alerts →
Free · No credit card · 60 sec setup
Affected Versions
go-vikunja / vikunja
>= 0.18.0, < 2.2.1
References
github.com: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-94xm-jj8x-3cr4 github.com: https://github.com/go-vikunja/vikunja/commit/033922309f492996c928122fb49b691339199c35 github.com: https://github.com/go-vikunja/vikunja/commit/04704e0fde4b027039cf583110cee7afe136fc1b github.com: https://github.com/go-vikunja/vikunja/commit/0b04768d830c80e9fde1b0962db1499cc652da0e github.com: https://github.com/go-vikunja/vikunja/commit/fd452b9cb6457fd4f9936527a14c359818f1cca7 vikunja.io: https://vikunja.io/changelog/vikunja-v2.2.2-was-released