Skip to main content
VulnerabilityPublished Updated

CVE-2026-28268: vikunja · Incomplete Cleanup

Affects vikunjaSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.8 Critical : upgrade to 2.1.0 as a priority.

Data as of 29 Oct 2026, 19:04 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Feb 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 29 Oct 2026.

What to do

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

Affected software

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

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

AI-suggested

Organizations should immediately upgrade all Vikunja instances to version 2.1.0 or later, which contains the patch that invalidates password reset tokens after use and corrects the token cleanup cron job. Until upgrade is possible, administrators should consider disabling the password reset functionality or implementing additional monitoring and alerting on reset token generation and usage. Review and secure logs and browser histories to prevent token leakage. Employ network security controls to limit exposure of Vikunja API endpoints, such as IP whitelisting or VPN access. Conduct user awareness training to reduce phishing risks that could lead to token interception. Additionally, implement multi-factor authentication (MFA) on user accounts to mitigate the impact of compromised credentials. Regularly audit token management and cleanup processes to ensure no residual tokens remain valid indefinitely.

Description

Vikunja is an open-source self-hosted task management platform. Versions prior to 2.1.0 have a business logic vulnerability exists in the password reset mechanism of vikunja/api that allows password reset tokens to be reused indefinitely. Due to a failure to invalidate tokens upon use and a critical logic bug in the token cleanup cron job, reset tokens remain valid forever. This allows an attacker who intercepts a single reset token (via logs, browser history, or phishing) to perform a complete, persistent account takeover at any point in the future, bypassing standard authentication controls. Version 2.1.0 contains a patch for the issue.

References

Community reviews

Loading reviews…