CVE-2026-33668
Vikunja is an open-source self-hosted task management platform. …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/go-vikunja/vikunja/commit/033922309f492996c928122fb49b691339199c35
- github.com/go-vikunja/vikunja/commit/04704e0fde4b027039cf583110cee7afe136fc1b
- github.com/go-vikunja/vikunja/commit/0b04768d830c80e9fde1b0962db1499cc652da0e
- github.com/go-vikunja/vikunja/commit/fd452b9cb6457fd4f9936527a14c359818f1cca7
- github.com/go-vikunja/vikunja/security/advisories/GHSA-94xm-jj8x-3cr4
- vikunja.io/changelog/vikunja-v2.2.2-was-released
- nvd.nist.gov/vuln/detail/CVE-2026-33668
- github.com/advisories/GHSA-94xm-jj8x-3cr4
- nvd.nist.gov/vuln/detail/CVE-2026-33668
- cve.org/CVERecord?id=CVE-2026-33668
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.