# CVE-2026-91970: Vikunja before 2.6.0 Resource Exhaustion via Planka Migration

> Authenticated attackers can cause denial of service in Vikunja by exploiting a resource exhaustion flaw in the Planka migration feature.

- **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
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Sep 2026
- **Updated:** 15 Sep 2026
- **Also known as:** GHSA-wq92-8x3r-fm38, GO-2026-6757

## What is CVE-2026-91970?

CVE-2026-91970 is a high-severity denial of service vulnerability in go-vikunja vikunja, published on 15 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Vikunja versions before 2.6.0 contain a resource exhaustion vulnerability in the Planka migrator that fails to enforce aggregate memory budgets during migration jobs. Authenticated attackers can submit migration requests pointing to attacker-controlled servers advertising numerous size-compliant attachments, exhausting worker memory and causing denial of service for all users.

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

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

3 open source packages ship an affected version, including code.vikunja.io/api.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `code.vikunja.io/api` | Go | All versions | None |
| `code.vikunja.io/api` | Go | From 2.5.0 | 2.6.0 |
| `code.vikunja.io/api` | Go | From 2.5.0 | 2.6.0 |

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

Upgrade code.vikunja.io/api to 2.6.0 or later.

## Is CVE-2026-91970 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-91970 is a high-severity denial of service vulnerability in go-vikunja vikunja, published on 15 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-91970 exists.

Affected packages and fixed versions:
- code.vikunja.io/api (Go): affected all versions; no fix listed
- code.vikunja.io/api (Go): affected from 2.5.0; fixed in 2.6.0
- code.vikunja.io/api (Go): affected from 2.5.0; fixed in 2.6.0

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

## Sources

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

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