Vikunja before 2.7.1 Resource Exhaustion via Vikunja-File ZIP Import
Affects Vikunja up to and including 2.7.0 for any authenticated user who can upload an export ZIP to the vikunja-file importer. CVSS scores it High (7.1). Fixed in 2.7.1.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.7.1
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affected product is Vikunja (code.vikunja.io/api) versions up to and including 2.7.0 (before 2.7.1). The attacker must be able to upload a Vikunja export ZIP to the vikunja-file ZIP importer.
- Last modified
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.30% · 22nd percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 15/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Vikunja before 2.7.1 contains a resource exhaustion vulnerability in the vikunja-file ZIP importer that allows authenticated users to consume CPU and memory by uploading archives with excessive entries. Attackers can upload export ZIPs containing many empty or non-files/ entries that bypass the per-entry caps, forcing scanArchive to process every entry twice.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Affected product is Vikunja (code.vikunja.io/api) versions up to and including 2.7.0 (before 2.7.1). The attacker must be able to upload a Vikunja export ZIP to the vikunja-file ZIP importer.Upgrade to a fixed version: 2.7.1.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- go-vikunja vikunja
fixed in 2.7.1
Evidence 2
- Advisory
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-123516
Is CVE-2026-123516 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
An authenticated user can upload a Vikunja export ZIP containing a very large number of empty or non-files/ entries. The importer then processes every entry twice, using extra CPU and memory. The advisory describes this as amplification bounded by the request body limit.Source: github.com
Which versions are affected by CVE-2026-123516?
vikunja: before 2.7.1.Source: cve.now feed data
Am I affected, and how do I check?
Vikunja (code.vikunja.io/api) versions up to and including 2.7.0 are affected; 2.7.1 is the first fixed version. To check a deployment, look at the Vikunja version it runs. The bug involves the vikunja-file ZIP importer, so whether that importer is reachable by authenticated users is the setting to review.Source: github.com
How do I fix CVE-2026-123516?
Upgrade Vikunja to version 2.7.1 or later. The facts provided do not list a workaround.Source: github.com