High severity · published Mar 24, 2026
CVE-2026-33668
Vikunja Allows Disabled/Locked User Accounts to Authenticate via API Tokens, CalDAV, and OpenID Connect
8.1
CVSS
0.5%
EPSS
No
On KEV
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.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Confidentiality
High
Integrity
High
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.5% · higher than 40% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
VI
vikunja · go-vikunja
>= 0.18.0, < 2.2.1 · source: vendor, NVD
Affected product
VI
vikunja
go-vikunja
More from vikunja
9.8
CVE-2026-28268
Vikunja Vulnerable to Account Takeover via Password Reset Token Reuse
9.6
CVE-2026-33334
Vikunja Desktop: Any frontend XSS escalates to Remote Code Execution due to nodeIntegration
9.1
CVE-2026-34727
Vikunja ahs a TOTP Two-Factor Authentication Bypass via OIDC Login Path
9.1
CVE-2026-27575
Vijkunja has Weak Password Policy Combined with Persistent Sessions After Password Change
8.8
CVE-2026-33336
Vikunja Desktop vulnerable to Remote Code Execution via same-window navigation