Vikunja from 2.4.0 before 2.7.1 contains an authorization bypass vulnerability that allows token holders to perform unintended operations due to colliding v1 and v2 API token permission keys. Attackers with a token scoped to read project backgrounds can delete them via the v2 DELETE background route, and bucket create-only tokens can update existing buckets.
Advisories
No advisories yet.
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
Sun, 08 Nov 2026 01:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Vikunja from 2.4.0 before 2.7.1 contains an authorization bypass vulnerability that allows token holders to perform unintended operations due to colliding v1 and v2 API token permission keys. Attackers with a token scoped to read project backgrounds can delete them via the v2 DELETE background route, and bucket create-only tokens can update existing buckets. | |
| Title | Vikunja 2.4.0 before 2.7.1 API Token Scope Collision Authorization Bypass | |
| First Time appeared |
Vikunja
Vikunja vikunja |
|
| Weaknesses | CWE-863 | |
| CPEs | cpe:2.3:a:vikunja:vikunja:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Vikunja
Vikunja vikunja |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: VulnCheck
Published:
Updated: 2026-11-08T01:37:36.283Z
Reserved: 2026-11-06T00:48:01.381Z
Link: CVE-2026-123527
No data.
Status : Deferred
Published: 2026-11-08T02:16:42.480
Modified: 2026-11-08T02:16:42.610
Link: CVE-2026-123527
No data.
OpenCVE Enrichment
Updated: 2026-11-08T03:30:15Z
Weaknesses