Vikunja from 0.23.0 before 2.7.1 contains an information disclosure vulnerability that allows project collaborators
Source GCVE Database
Not known to be exploited · CVSS 6.9 Medium : upgrade to 2.7.1 when convenient.
Data as of 8 Nov 2026, 06:49 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
A fix for this vulnerability is available in Vikunja version 2.7.1 and later. Users should upgrade to version 2.7.1 or newer to remediate this issue. Since no vendor advisory or patch links are provided, confirm patch availability from official Vikunja sources before upgrading. Until patched, restrict write access to trusted collaborators only to reduce risk.
Description
Vikunja versions from 0.23.0 up to but not including 2.7.1 have an information disclosure vulnerability. Project collaborators with write access can exploit this flaw by registering webhooks to read tasks from projects they should not access. The webhook payloads are generated with the permissions of the user triggering the event, allowing attackers to obtain titles, descriptions, and metadata of tasks from private projects when linked tasks are modified.