Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
7.4

Vikunja skips two‑factor check on OIDC login

CVE-2026-34727 · published 6 months ago
Summary

The open‑source task manager Vikiknja could let a user who normally uses a verification code sign in without entering it when they log in through an external identity provider. This happens because the system gave a full access token without confirming the extra security step. Upgrade to version 2.3.0 or later to restore proper two‑factor protection.

What to do
  • Update code.vikunja.io api to version 2.3.0.
  • Update vikunja vikunja to version 2.3.0 or later.
Affected software
Ecosystem VendorProductAffected versions
go code.vikunja.io api <= 2.2.2
Fix: upgrade to 2.3.0
– vikunja vikunja < 2.3.0
cpe:2.3:a:vikunja:vikunja:*:*:*:*:*:*:*:*
Original advisory text
Vikunja ahs a TOTP Two-Factor Authentication Bypass via OIDC Login Path
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.
References
Fix within
Internet-facing 14 days
Internal At next upgrade
  • Not known to be exploited
  • Needs hands-on effort to exploit
  • Gives an attacker full control
Severity
7.4 High
Exploitation
<1% chance of attack within 30 days
Type
CWE-287Improper Authentication
Timeline
Published10 Apr 2026
Updated3 Nov 2026
First seen10 Apr 2026
Sources
CVE-2026-34727 · NVD
GHSA-8jvc-mcx6-r4cg · GHSA
CVE-2026-34727 · OSV
Track software like this
Free during beta