CVE-2026-33668
High
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.
SeverityHigh
CVSS8.1
Exploit probability—
ProductVikunja
PublishedMar 24, 2026
First seenMar 24, 2026
Weakness typeCWE-285CWE-285CWE-863Incorrect authorization
How to fix
Update
- vikunja vikunja2.2.1 or later
- code.vikunja.io/api2.2.1 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| vikunja vikunja | 0.18.0 ≤ v < 2.2.1 | 2.2.1 |
| code.vikunja.io/apiGo | 0.18.0 ≤ v < 2.2.1, 0.18.0 ≤ v | 2.2.1 |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
In the Intelligence 360 plan
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.