CVE-2026-33668 | THREATINT

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.

PUBLISHED Reserved 2026-03-23 | Published 2026-03-24 | Updated 2026-03-26 | Assigner GitHub_M

HIGH: 7.1CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Problem types

CWE-285: Improper Authorization

CWE-863: Incorrect Authorization

Product status

>= 0.18.0, < 2.2.1

affected

References

github.com/...ikunja/security/advisories/GHSA-94xm-jj8x-3cr4

github.com/...ommit/033922309f492996c928122fb49b691339199c35

github.com/...ommit/04704e0fde4b027039cf583110cee7afe136fc1b

github.com/...ommit/0b04768d830c80e9fde1b0962db1499cc652da0e

github.com/...ommit/fd452b9cb6457fd4f9936527a14c359818f1cca7

vikunja.io/changelog/vikunja-v2.2.2-was-released

cve.org (CVE-2026-33668)

nvd.nist.gov (CVE-2026-33668)

Download JSON