What’s Vulnerable › Vulnerabilities

CVE-2026-33316: Vikunja’s Improper Access Control Enables Bypass of Administrator-Imposed Account Disablement

• Severity: high (CVSS 8.1 v3.1)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 0.4% probability of exploitation in the next 30 days
• Public exploit or detection template: yes
• Published: 2026-03-24 · updated 2026-06-17
• Weakness: CWE-284

Description

Vikunja is an open-source self-hosted task management platform. Prior to version 2.2.0, a flaw in Vikunja’s password reset logic allows disabled users to regain access to their accounts. The `ResetPassword()` function sets the user’s status to `StatusActive` after a successful password reset without verifying whether the account was previously disabled. By requesting a reset token through `/api/v1/user/password/token` and completing the reset via `/api/v1/user/password/reset`, a disabled user can reactivate their account and bypass administrator-imposed account disablement. Version 2.2.0 patches the issue.

Affected products

• go-vikunja vikunja: before 2.2.0 — fixed in 2.2.0

How to fix

Upgrade to a fixed version: go-vikunja vikunja 2.2.0. Check the vendor advisory for mitigations.

References

• https://github.com/go-vikunja/vikunja/commit/049f4a6be46f9460bd516f489ef9f569574bc70d
• https://github.com/go-vikunja/vikunja/commit/d8570c603da1f26635ce6048d6af85ede827abfb
• https://github.com/go-vikunja/vikunja/security/advisories/GHSA-vq4q-79hh-q767
• https://vikunja.io/changelog/vikunja-v2.2.0-was-released

Get alerted when CVE-2026-33316 or the next vulnerability affects your stack