CVE-2026-40103 Details
Description
Vikunja is an open-source self-hosted task management platform. Prior to 2.3.0, Vikunja's scoped API token enforcement for custom project background routes is method-confused. A token with only projects.background can successfully delete a project background, while a token with only projects.background_delete is rejected. This is a scoped-token authorization bypass. This vulnerability is fixed in 2.3.0.
A scoped API token authorization bypass vulnerability has been identified in Vikunja, a self-hosted task management platform, prior to version 2.3.0. The issue arises from method confusion in the token enforcement for custom project background routes. A token granted the 'projects.background' permission can successfully delete a project background, while a token with 'projects.background_delete' is denied. This vulnerability allows tokens to exceed their intended capabilities, particularly in automated processes and third-party integrations that rely on precise token scopes.
Users are advised to update Vikunja to version 2.3.0 or later, where this vulnerability has been fixed.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Apr 15, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-836 | Use of Password Hash Instead of Password for Authentication | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| vikunja vikunja | < 2.3.0 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Apr 17, 2026 | Initial Analysis | [email protected] |
| Apr 10, 2026 | New CVE Received | [email protected] |