CVE-2026-40103: Vikunja's Scoped API tokens with projects.background permission can delete project backgrounds
go-vikunja · vikunja
Affected: go-vikunja vikunja · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 13% of scored CVEs
DescriptionCVE.org
Vikunja is an open-source self-hosted task management platform. Prior to 2.3.0, Vikunja's scoped API token enforcement for custom project background routes is method-confused. A token with only projects.background can successfully delete a project background, while a token with only projects.background_delete is rejected. This is a scoped-token authorization bypass. This vulnerability is fixed in 2.3.0.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- go-vikunja · vikunja< 2.3.0
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- go-vikunja
- Published
- April 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-40103 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.
References
- NVD entrynvd.nist.gov
- CVE recordcve.org
- Weakness CWE-836cwe.mitre.org
- github.com/go-vikunja/vikunja/security/advisories/GHSA-v479-vf79github.com
- github.com/go-vikunja/vikunja/pull/2584github.com
- github.com/go-vikunja/vikunja/commit/6a0f39b252a81fa4b19dc56dc88github.com
- github.com/go-vikunja/vikunja/releases/tag/v2.3.0github.com