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.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/go-vikunja/vikunja/security/advisories/GHSA-qh78-rvg3-cv54 Exploit, Vendor Advisory
- https://github.com/go-vikunja/vikunja/security/advisories/GHSA-qh78-rvg3-cv54 Exploit, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 7.1 · vikunjaNVD modified 2026-10-26 21:10
Affected (CPE criteria) 1
cpe:2.3:a:vikunja:vikunja:*:*:*:*:*:*:*:*
References 4
- https://github.com/go-vikunja/vikunja/pull/2575 Issue Tracking
- https://github.com/go-vikunja/vikunja/releases/tag/v2.3.0 Release Notes
- https://github.com/go-vikunja/vikunja/security/advisories/GHSA-qh78-rvg3-cv54 Exploit, Vendor Advisory
- https://github.com/go-vikunja/vikunja/security/advisories/GHSA-qh78-rvg3-cv54 Exploit, Vendor Advisory