Resource exhaustion in Go-Vikunja Vikunja
CVE-2026-35602
Vikunja is an open-source self-hosted task management platform. Prior to 2.3.0, the Vikunja file import endpoint uses the attacker-controlled Size field from the JSON metadata inside the import zip instead of the actual decompressed file content length for the file size enforcement check. By setting Size to 0 in the JSON while including large compressed file entries in the zip, an attacker bypasses the configured maximum file size limit. This vulnerability is fixed in 2.3.0.
EPSS: 0.003 (26.3th percentile) — read the EPSS interpretation.
CVSS v3 metric
CVSS v3 base score 5.4 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L.
Affected products
- Go-vikunja Vikunja — versions < 2.3.0
- Vikunja
Weakness classification (CWE)
References
- security-advisories@github.com (x_refsource_CONFIRM, Exploit, Vendor Advisory)
- security-advisories@github.com (x_refsource_MISC, Issue Tracking)
- security-advisories@github.com (x_refsource_MISC, Release Notes)
Frequently asked questions
- What is CVE-2026-35602?
- CVE-2026-35602 is a medium-severity vulnerability in Go-Vikunja Vikunja, classified under Allocation of Resources Without Limits or Throttling. CVSS score: 5.4/10. Published 2026-04-10.
- How severe is CVE-2026-35602?
- Medium severity. CVSS v3 base score is 5.4 out of 10.