CVE-2026-33316: Vikunja’s Improper Access Control Enables Bypass of Administrator-Imposed Account Disablement
(updated )
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.
References
- github.com/advisories/GHSA-vq4q-79hh-q767
- github.com/go-vikunja/vikunja
- github.com/go-vikunja/vikunja/commit/049f4a6be46f9460bd516f489ef9f569574bc70d
- github.com/go-vikunja/vikunja/commit/d8570c603da1f26635ce6048d6af85ede827abfb
- github.com/go-vikunja/vikunja/security/advisories/GHSA-vq4q-79hh-q767
- nvd.nist.gov/vuln/detail/CVE-2026-33316
- vikunja.io/changelog/vikunja-v2.2.0-was-released
Code Behaviors & Features
Detect and mitigate CVE-2026-33316 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →