CVE-2026-123527go-vikunja vikunja Incorrect Authorization
NVD
Vulnerability Summary
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.
CVSS v4.0 Base Metrics — Score 5.3 (MEDIUM)
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:NAttack VectorNetwork
Attack ComplexityLow
Attack RequirementsNone
Privileges RequiredLow
User InteractionNone
Confidentiality (Vulnerable System)None
Integrity (Vulnerable System)Low
Availability (Vulnerable System)Low
Confidentiality (Subsequent System)None
Integrity (Subsequent System)None
Availability (Subsequent System)None
Show CVSS v3.x metrics (score 5.4)
CVSS v3.1 Base Metrics — Score 5.4 (MEDIUM)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:LAttack VectorNetwork
Attack ComplexityLow
Privileges RequiredLow
User InteractionNone
ScopeUnchanged
ConfidentialityNone
IntegrityLow
AvailabilityLow
Affected & Patched Versions
- go-vikunja vikunja >= 2.4.0 and < 2.7.1
- go-vikunja vikunja 2.7.1
What to do
Fix it during your normal patch cycle. No exploitation is confirmed yet.
- Check whether you run go-vikunja vikunja and which version.
- Update to a patched version listed above, then confirm the new version.
Timeline
- Nov 8, 2026Published
- Nov 12, 2026Record last modified
Score, severity and exploitation changes are tracked from the day Watchtower started logging them.
Get notified about new go-vikunja vikunja CVEsYou are reading CVE-2026-123527. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alertsExternal References
Data last checked: Nov 14, 2026 03:11 UTC