# CVE-2026-123516: Vikunja resource exhaustion in ZIP file importer

Source: https://junglewise.ai/threats/cve-2026-123516-vikunja-before-2-7-1-contains-a-resource-exhaustion  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-08. Updated: 2026-11-08  
License: CC BY 4.0 with a link back

CVE-2026-123516 · Severity: medium · CVSS 4.3 · Published 2026-11-08

Vikunja is a task management and project planning tool that allows users to import data from backup files. An authenticated attacker can upload a specially crafted ZIP file with an excessive number of entries to exhaust the server's CPU and memory resources, potentially causing service degradation or denial of service.

Technologies: [Vikunja](https://junglewise.ai/threats/technologies/vikunja). Vendors: [Vikunja](https://junglewise.ai/threats/vendors/vikunja).

## Quick answers

**Is CVE-2026-123516 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-123516 being exploited in the wild.

**How severe is CVE-2026-123516?** Medium severity, with a CVSS score of 4.3, published 8 November 2026.

**Which products and versions are affected?** Vikunja before 2.7.1.

**Is there a fix for CVE-2026-123516?** Yes: fixed in 2.7.1. Until then: Restrict ZIP file imports to trusted users, or temporarily disable the vikunja-file ZIP importer until the patch can be deployed. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-123516 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-123516?** Check whether you run Vikunja at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in 2.7.1

Restrict ZIP file imports to trusted users, or temporarily disable the vikunja-file ZIP importer until the patch can be deployed.

## Technical details

The vulnerability is a resource exhaustion flaw in the vikunja-file ZIP importer (scanArchive function in pkg/modules/migration/vikunja-file/vikunja.go) that lacks a cap on the total number of entries in a ZIP archive. Attackers can bypass per-entry size caps by including many empty entries that are processed twice—once during validation and again during migration. The impact is linear in upload size (approximately 76 bytes per entry) and bounded by the request body limit.

## Affected products

- Vikunja Vikunja before 2.7.1

## Timeline

- 2026-10-22: disclosed
- 2026-11-08: advisory
- 2026-11-08: patched

## References

- [https://github.com/go-vikunja/vikunja/security/advisories/GHSA-mqq8-869v-48q8](https://github.com/go-vikunja/vikunja/security/advisories/GHSA-mqq8-869v-48q8)
- [https://www.vulncheck.com/advisories/vikunja-before-2.7.1-resource-exhaustion-via-vikunja-file-zip-import](https://www.vulncheck.com/advisories/vikunja-before-2.7.1-resource-exhaustion-via-vikunja-file-zip-import)

## Related threats

- [Vikunja denial of service via pagination bypass in API v1](https://junglewise.ai/threats/cve-2026-123531-vikunja-from-1-0-0-before-2-7-1-contains-an-uncontrolled)
- [Vikunja missing authentication in TOTP enrollment](https://junglewise.ai/threats/cve-2026-123530-vikunja-before-2-7-1-contains-a-missing-authentication)
- [Vikunja stored CSS injection in rich-text table cells](https://junglewise.ai/threats/cve-2026-123529-vikunja-before-2-7-1-contains-a-stored-css-injection)
- [Vikunja insufficient session expiration in HTTP token middleware](https://junglewise.ai/threats/cve-2026-123528-vikunja-before-2-7-1-contains-an-insufficient-session-expiration)
- [Vikunja API token authorization bypass in v1/v2 collision](https://junglewise.ai/threats/cve-2026-123527-vikunja-from-2-4-0-before-2-7-1-contains-an-authorization-bypass)