Skip to main content
VulnerabilityPublished Updated

CVE-2026-34727: vikunja · Improper Authentication

Affects vikunjaSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.4 High : upgrade to 2.3.0 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
7.4High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.3.0
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade vikunja and github.com/go-vikunja/vikunja to 2.3.0.

Affected software

ProductAffectedFixed in
go-vikunjavikunjaAffected
  • <2.3.0
Fixed in
  • 2.3.0
Gogithub.com/go-vikunja/vikunjapkg:golang/github.com/go-vikunja/vikunjaOther threatsAffected
  • <2.3.0
Fixed in
  • 2.3.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Vikunja to version 2.3.0 or later, where this vulnerability is fixed. Since the vendor advisory indicates the issue is resolved in 2.3.0, applying this official fix is the recommended remediation. Patch status is not explicitly stated beyond this version fix, so verify with the vendor for any additional guidance.

Description

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

Community reviews

Loading reviews…