Skip to main content
VulnerabilityPublished

CVE-2026-33315: vikunja · Authentication Bypass Using an Alternate Path or Channel

Affects vikunjaSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.9 Medium : upgrade to 2.2.0 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.2.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Mar 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.2.0.

Affected software

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

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

AI-suggested

Organizations using vikunja versions prior to 2.2.0 should upgrade immediately to version 2.2.0 or later, which patches the authentication bypass vulnerability. If immediate upgrade is not feasible, administrators should consider disabling the Caldav endpoint or restricting its network access to trusted internal networks only. Implement network-level controls such as firewalls or VPNs to limit exposure of the Caldav service. Additionally, review and enforce strong password policies to reduce the risk of credential compromise, as the vulnerability relies on valid credentials. Monitoring access logs for unusual authentication attempts on the Caldav endpoint can help detect exploitation attempts. Finally, consider implementing additional compensating controls such as IP whitelisting or multi-factor authentication enforcement at the network gateway level until the patch is applied.

Description

Vikunja is an open-source self-hosted task management platform. Prior to version 2.2.0, the Caldav endpoint allows login using Basic Authentication, which in turn allows users to bypass the TOTP on 2FA-enabled accounts. The user can then access standard project information that would normally be protected behind 2FA (if enabled), such as project name, description, etc. Version 2.2.0 patches the issue.

References

Community reviews

Loading reviews…