CVE-2026-33668
Vikunja broken access control
- Published24 Mar 2026
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 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:NAffected products
Remediation
- 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
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
- https://vikunja.io/changelog/vikunja-v2.2.2-was-released
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-33668 being actively exploited?
CVE-2026-33668 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.59%.
How severe is CVE-2026-33668?
CVE-2026-33668 has a CVSS 3.1 base score of 8.1, rated high. EPSS estimates a 0.59% probability of exploitation.
Which products are affected by CVE-2026-33668?
Affected products include Vikunja.
How do I fix CVE-2026-33668?
Upgrade affected software to a fixed version, for example Vikunja 2.2.1 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-33668 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.