Vikunja is an open-source self-hosted task management platform. Prior to 2.3.0, the OIDC callback handler issues a full JWT token without checking whether the matched user has TOTP two-factor authentication enabled. When a local user with TOTP enrolled is matched via the OIDC email fallback mechanism, the second factor is completely skipped. This vulnerability is fixed in 2.3.0.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/go-vikunja/vikunja/security/advisories/GHSA-8jvc-mcx6-r4cg Exploit, Vendor Advisory
- https://github.com/go-vikunja/vikunja/security/advisories/GHSA-8jvc-mcx6-r4cg Exploit, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 9.1 · vikunjaNVD modified 2026-10-26 00:10
Affected (CPE criteria) 1
cpe:2.3:a:vikunja:vikunja:*:*:*:*:*:*:*:*
References 2
- https://github.com/go-vikunja/vikunja/security/advisories/GHSA-8jvc-mcx6-r4cg Exploit, Vendor Advisory
- https://github.com/go-vikunja/vikunja/security/advisories/GHSA-8jvc-mcx6-r4cg Exploit, Vendor Advisory