# CVE-2026-123519: Vikunja before 2.7.1 Memory Exhaustion DoS via WeKan and Vikunja-File Imports


- **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-94xf-3vwp-m22j, GHSA-g2xc-jv9q-46wq

## What is CVE-2026-123519?

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

### Official description

Vikunja before 2.7.1 contains a denial of service vulnerability that allows authenticated users to exhaust API process memory by uploading WeKan or vikunja-file imports with no item-count cap. Attackers can submit a ~22 MB WeKan JSON with hundreds of thousands of cards or duplicate IDs to the wekan migrate endpoint, triggering OOM and crashing the instance.

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

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


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

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

## Is CVE-2026-123519 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-123519 is a high-severity vulnerability in go-vikunja vikunja, published on 8 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-123519 exists.

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-123519/ (Markdown: https://insights.sbomify.com/CVE-2026-123519/index.md)
```

## Sources

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

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