CVE-2026-35602 Vikunja has a File Size Limit Bypass via Vikunja Import

Medium 5.4 Published Updated

Attackers bypass file size limits in Vikunja imports by manipulating JSON metadata, potentially causing resource exhaustion or denial of service.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-35602?

CVE-2026-35602 is a medium-severity vulnerability in go-vikunja vikunja, published on 10 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

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.

Weakness: CWE-770

Which versions are affected by CVE-2026-35602?

3 open source packages ship an affected version, including code.vikunja.io/api. It affects 1 product.

PackageAffectedFixed in
code.vikunja.io/api GoAll versionsNone
code.vikunja.io/api GoAll versions2.3.0
code.vikunja.io/api GoAll versions2.3.0

Products include Vikunja Vikunja.

How do I fix CVE-2026-35602?

Upgrade code.vikunja.io/api to 2.3.0 or later.

Is CVE-2026-35602 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35602 exists.

Sources

Also known as GHSA-qh78-rvg3-cv54, GO-2026-5582.

Is CVE-2026-35602 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free