Auth bypass in Go-Vikunja Vikunja
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 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.
Vulnerability class: Broken Access Control
Published · last modified .
CVSS v3 metric
CVSS v3 base score 5.4 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L.
EPSS exploit prediction
No EPSS score from FIRST.org yet. New CVEs usually get one within a few days; no score means no signal yet, not low risk. How EPSS works.
Affected products
Weakness classification (CWE)
References
- GitHub Security Advisory (GHSA-j5v7-qcwp-5g32) (vendor-advisory)
- VulnCheck Advisory: Vikunja 2.4.0 before 2.7.1 API Token Scope Collision Authorization Bypass (third-party-advisory)
Frequently asked questions
- What is CVE-2026-123527?
- CVE-2026-123527 is a medium-severity vulnerability in Go-Vikunja Vikunja, classified under Incorrect Authorization. CVSS score: 5.4/10. Published 2026-11-08.
- How severe is CVE-2026-123527?
- Medium severity. CVSS v3 base score is 5.4 out of 10.