go-vikunja up to 2.2.x File Import Endpoint Size allocation of resources

Summaryinfo

A vulnerability identified as problematic has been detected in go-vikunja vikunja up to 2.2.x. This issue affects some unknown processing of the component File Import Endpoint. The manipulation of the argument Size leads to allocation of resources. This vulnerability is referenced as CVE-2026-35602. Remote exploitation of the attack is possible. No exploit is available. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in go-vikunja vikunja up to 2.2.x and classified as problematic. This issue affects some unknown functionality of the component File Import Endpoint. The manipulation of the argument Size with an unknown input leads to a allocation of resources vulnerability. Using CWE to declare the problem leads to CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. Impacted is integrity, and availability. The summary by CVE is:

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.

It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2026-35602 since 04/03/2026. The exploitation is known to be easy. The attack may be initiated remotely. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1499 according to MITRE ATT&CK.

Upgrading to version 2.3.0 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Vendor

• go-vikunja

Name

• vikunja

Version

• 2.0
• 2.1
• 2.2

Website

• Product: https://github.com/go-vikunja/vikunja/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion