CVE-2026-123524: vikunja · Incorrect Authorization
Affects vikunjaSource CVE Database V5
Not known to be exploited · CVSS 6.9 Medium : upgrade to 2.7.1 when convenient.
Data as of 8 Nov 2026, 02:18 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 6.9 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 5.7 |
- Patch
- Available – fixed in 2.7.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 8 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 7 Nov 2026.
What to do
Upgrade vikunja to 2.7.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| go-vikunjavikunja | Affected
| Fixed in
|
Govikunjapkg:golang/vikunjaOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Vikunja to version 2.7.1 or later, where this authorization vulnerability is fixed. No other mitigation or temporary workaround is indicated by the vendor advisory.
Description
Vikunja versions from 0.23.0 up to but not including 2.7.1 have an authorization flaw that allows project collaborators with write access to access task details from projects they should not have access to. This occurs via webhook registration, where webhook payloads are generated with the triggering user's permissions, exposing titles, descriptions, and metadata of tasks in private projects when linked tasks are modified. The vulnerability is fixed in version 2.7.1.