CVE-2026-33668
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.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (0.45%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
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 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:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/M
- EPSS
- 0.45% probability · 38th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-285, CWE-863
- Affected
- vikunja/vikunja
- Source
- security-advisories@github.com
References
- https://github.com/go-vikunja/vikunja/commit/033922309f492996c928122fb49b691339199c35Patch
- https://github.com/go-vikunja/vikunja/commit/04704e0fde4b027039cf583110cee7afe136fc1bPatch
- https://github.com/go-vikunja/vikunja/commit/0b04768d830c80e9fde1b0962db1499cc652da0ePatch
- https://github.com/go-vikunja/vikunja/commit/fd452b9cb6457fd4f9936527a14c359818f1cca7Patch
- https://github.com/go-vikunja/vikunja/security/advisories/GHSA-94xm-jj8x-3cr4Exploit, Vendor Advisory
- https://vikunja.io/changelog/vikunja-v2.2.2-was-releasedRelease Notes
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.