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.
Use CWE-285, Vikunja vendor hub and Vikunja product page to widen CVE-2026-33668 into its surrounding weakness, vendor, and product context.
Compare it with CVE-2026-35595, CVE-2026-34727 and CVE-2026-33700 for nearby disclosures in the same product family.