NIXPKGS-2026-0484
GitHub issue
published 3 months, 3 weeks ago
Permalink
CVE-2026-28268
9.8 CRITICAL
- CVSS version (CVSS): 3.1
- Attack Vector (AV): Network (N)
- Attack Complexity (AC): Low (L)
- Privileges Required (PR): None (N)
- User Interaction (UI): None (N)
- Scope (S): Unchanged (U)
- Confidentiality (C): High (H)
- Integrity (I): High (H)
- Availability (A): High (H)
- Modified Attack Vector (MAV): Network (N)
- Modified Attack Complexity (MAC): Low (L)
- Modified Privileges Required (MPR): None (N)
- Modified User Interaction (MUI): None (N)
- Modified Confidentiality (MC): High (H)
- Modified Scope (MS): Unchanged (U)
- Modified Integrity (MI): High (H)
- Modified Availability (MA): High (H)
by @LeSuisse Activity log
- Created suggestion
- @LeSuisse ignored package vikunja-desktop
- @LeSuisse added maintainer @adamcstephens maintainer.add
- @LeSuisse accepted
- @LeSuisse published on GitHub
Vikunja Vulnerable to Account Takeover via Password Reset Token Reuse
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
-
https://github.com/go-vikunja/vikunja/security/advisories/GHSA-rfjg-6m84-crj2 x_refsource_CONFIRM
-
https://vikunja.io/changelog/vikunja-v2.1.0-was-released x_refsource_MISC
Affected products
vikunja
- ==< 2.1.0
Package maintainers
-
@leona-ya Leona Maroni <nix@leona.is>
Additional maintainers
-
@adamcstephens Adam C. Stephens <happy.plan4249@valkor.net>