CVE-2026-123514: vikunja · Uncontrolled Resource Consumption
Affects vikunjaSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium : upgrade to 2.7.1 when convenient.
Data as of 8 Nov 2026, 02:19 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 5.3 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 4.3 |
- Patch
- Available – fixed in 2.7.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/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 to Vikunja version 2.7.1 or later, where this improper resource cleanup vulnerability has been fixed. No other specific mitigations are indicated.
Description
Vikunja versions prior to 2.7.1 have a vulnerability where full-data export archives are not properly cleaned up after exports or account deletions. Authenticated users can repeatedly trigger exports, causing orphaned data archives to accumulate and exhaust disk storage. Additionally, personal data of deleted users remains on disk indefinitely.