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


- **Severity:** High 7.1 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 8 Nov 2026
- **Updated:** 12 Nov 2026
- **Also known as:** GHSA-5gjc-rq8x-g8fj, GHSA-mqq8-869v-48q8

## What is CVE-2026-123516?

CVE-2026-123516 is a high-severity vulnerability in go-vikunja vikunja, published on 8 Nov 2026. 

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

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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


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

No fix has been published for CVE-2026-123516 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-123516 being exploited?

There is no known exploitation of CVE-2026-123516 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-123516 and fix it if it is affected.

What it is: CVE-2026-123516 is a high-severity vulnerability in go-vikunja vikunja, published on 8 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-123516 in the wild and no public exploit code.

Affected product: go-vikunja vikunja. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-123516/ (Markdown: https://insights.sbomify.com/CVE-2026-123516/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-123516
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-123516
- OSV: https://osv.dev/vulnerability/CVE-2026-123516

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-123516/
Summaries are generated and may contain mistakes; the official description above is the record.