CVE-2026-123527 · Package
NO FIX YET · SEE WHAT TO DO
Vikunja versions from 2.4.0 before 2.7.1 mix up v1 and v2 API token permission keys, so a token scoped for one action can perform others. An attacker holding a read-only background token can delete project backgrounds, and a bucket create-only token can update existing buckets.
first public Oct 22, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Teams that self-host Vikunja between versions 2.4.0 and 2.7.1 and issue API tokens to users or automations. Instances on 2.7.1 or later, or those not using API tokens, are not exposed.
Not affected if no-api-tokens, version-2.7.1-or-later
Who cares api-tokens, self-hosted, vikunja
2.4.0 up to but not including 2.7.12.7.1 or laterVikunja 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.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.