CVE-2026-33668 json
Vikunja Allows Disabled/Locked User Accounts to Authenticate via API Tokens, CalDAV, and OpenID Connect
published 2026-03-24 7 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-14913 , GHSA-94xm-jj8x-3cr4 , GO-2026-4849
- cvss
- 8.1
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 40%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go code.vikunja.io/api 2.2.1
- vikunja vikunja 2.2.1
- govulncheck-vulndb openSUSE Leap 15.6 0.0.20260326T203309-150000.1.155.2
suse advisories SUSE-SU-2026:1135-1
- govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
opensuse advisories openSUSE-SU-2026:21483-1
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 7 mo ago
Exploit prediction
0.46% chance of exploitation in the next 30 days, higher than 40% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/go-vikunja/vikunja/security/advisories/GHSA-94xm-jj8x-3cr4 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 7.1 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N |
| CNA | 4.0 | 7.1 | CVSS: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/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| NVD | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | code.vikunja.io/api | >=0.18.0, <2.2.1 >=0.18.0 |
2.2.1 |
Affected products
- go-vikunja vikunja
Classification
References
-
github.com
/go-vikunja/vikunja/commit/033922309f492996c928122fb49b691339199c35
web, patch
-
github.com
/go-vikunja/vikunja/commit/04704e0fde4b027039cf583110cee7afe136fc1b
web, patch
-
github.com
/go-vikunja/vikunja/commit/0b04768d830c80e9fde1b0962db1499cc652da0e
web, patch
-
github.com
/go-vikunja/vikunja/commit/fd452b9cb6457fd4f9936527a14c359818f1cca7
web, patch
-
github.com
/go-vikunja/vikunja/security/advisories/GHSA-94xm-jj8x-3cr4
web, exploit, vendor-advisory, advisory
-
vikunja.io
/changelog/vikunja-v2.2.2-was-released
web, release-notes
-
nvd.nist.gov
/vuln/detail/CVE-2026-33668
advisory
-
github.com
/go-vikunja/vikunja
package
Sources
- CVE List CVE-2026-33668
- GitHub Advisory GHSA-94xm-jj8x-3cr4
- NVD CVE-2026-33668
- OSV GO-2026-4849
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.