CVSS 4.0
7.1 highCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:NCVE-2026-33668
High (7.1) in vikunja vikunja. EPSS 0.5% chance of exploitation in the next 30 days. Fixed in code.vikunja.io/api 2.2.1.
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.
Severity
CVSS 3.1
8.1 highCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N- EPSS
- 0.5% chance of exploitation in the next 30 days; higher than 39% of CVEs (scores of 2026-10-31)
- CWEs
- CWE-285, CWE-863
- Published
- Modified
- Record from
- the NVD, synced
Affected
- vikunja:vikunja
Packages (OSV)
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-94xm-jj8x-3cr4 | Go | code.vikunja.io/api | >=0.18.0 <2.2.1 | 2.2.1 |
| GO-2026-4849 | Go | code.vikunja.io/api | >=0.18.0 | no fix published |
References
- https://github.com/go-vikunja/vikunja/commit/033922309f492996c928122fb49b691339199c35
- https://github.com/go-vikunja/vikunja/commit/04704e0fde4b027039cf583110cee7afe136fc1b
- https://github.com/go-vikunja/vikunja/commit/0b04768d830c80e9fde1b0962db1499cc652da0e
- https://github.com/go-vikunja/vikunja/commit/fd452b9cb6457fd4f9936527a14c359818f1cca7
- https://github.com/go-vikunja/vikunja/security/advisories/GHSA-94xm-jj8x-3cr4