medium5.3
CVE-2026-123527
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 a…
Impact
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.
An attacker can exploit this over the network, with a regular user account, without any action by a user. If it succeeds: low risk of data or systems being changed, low risk of outages.
Affected products · Go-vikunja
| Product | Affected versions |
|---|---|
| Vikunja | from 2.4.0 before 2.7.1 |
Weakness classification
References
- NVD record
- CVE.org record
- GitHub advisory
- https://github.com/go-vikunja/vikunja/security/advisories/GHSA-j5v7-qcwp-5g32
- https://www.vulncheck.com/advisories/vikunja-2.4.0-before-2.7.1-api-token-scope-collision-authorization-bypass
- https://github.com/advisories/GHSA-w4rp-qjww-56rf
- https://nvd.nist.gov/vuln/detail/CVE-2026-123527