CVE-2026-33668
March 24, 2026
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.
Affected Packages
code.vikunja.io/api (GO):
Affected version(s) >=v0.18.0 <v2.2.1Fix Suggestion:
Update to version v2.2.1code.vikunja.io/api (GO):
Affected version(s) >=v0.18.0 <v2.2.1Fix Suggestion:
Update to version v2.2.1github.com/go-vikunja/vikunja (GO):
Affected version(s) >=v0.18.0 <v2.2.1Fix Suggestion:
Update to version v2.2.1code.vikunja.io/api (GO):
Affected version(s) >=v0.18.0 <v2.2.1Fix Suggestion:
Update to version v2.2.1github.com/go-vikunja/vikunja (GO):
Affected version(s) >=v0.18.0 <v2.2.1Fix Suggestion:
Update to version v2.2.1github.com/go-vikunja/vikunja (GO):
Affected version(s) >=v0.18.0 <v2.2.1Fix Suggestion:
Update to version v2.2.1Related Resources (8)
Do you need more information?
Contact UsCVSS v4
Base Score:
7.1
Attack Vector
NETWORK
Attack Complexity
LOW
Attack Requirements
NONE
Privileges Required
LOW
User Interaction
NONE
Vulnerable System Confidentiality
NONE
Vulnerable System Integrity
HIGH
Vulnerable System Availability
NONE
Subsequent System Confidentiality
NONE
Subsequent System Integrity
NONE
Subsequent System Availability
NONE
CVSS v3
Base Score:
6.5
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
HIGH
Availability
NONE
EPSS
Base Score:
0.19
