Skip to main content
Menu
CVEs

Go Vikunja API denial of service in user export amplification

CVE-2026-134269Published November 21, 2026, updated

7.1HighCNA
Exploited
No known exploitation
Fix
Fixed in 2.8.0
Who is exposed
Specific setups only

Summary

Vikunja from 0.18.0 before 2.8.0 contains a resource amplification vulnerability in pkg/models/export.go that allows authenticated users to exhaust server memory by exporting heavily related tasks. Attackers can relate many tasks to one task with a large description and request a user export, causing an out-of-memory crash for all users.

Who should check

Teams running Vikunja (go-vikunja/vikunja) versions 0.18.0 through 2.7.1, or Go services importing code.vikunja.io/api

“>= 0.18.0, <= 2.7.1”

github.com

What to do

  1. Check whether your setup matches what the bug needs.

    Vikunja versions 0.18.0 through 2.7.1 are affected; 2.8.0 is the patched version.
  2. Upgrade to a fixed version: 2.8.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-134269 (Vikunja 0.18.0 before 2.8.0 Denial of Service via User Export Amplification), 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-134269 (entry last updated 2026-11-21):
Affected:
- Go package code.vikunja.io/api: from 0.18.0, fixed in 2.8.0
Fixed versions: 2.8.0.
Conditions (all must be true for the bug to be hit):
- Vikunja versions 0.18.0 through 2.7.1 are affected; 2.8.0 is the patched version. (source: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-mmvj-p6vj-f83v)
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-134269 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134269 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-mmvj-p6vj-f83v
- https://www.vulncheck.com/advisories/vikunja-0.18.0-before-2.8.0-denial-of-service-via-user-export-amplification
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-134269
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-134269"}.

Affected versions

cve.now Index

25Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach10/20Affects Go packages
  • Severity7.1/10CVSS 7.1
  • No patch0/5No signal

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active
  • Would score about 32 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · go-vikunja/vikunja · Advisory GHSA-mmvj-p6vj-f83v
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134269
RecordNVD · CVE-2026-134269
Other links 1
Linkvulncheck.com · advisories/vikunja-0.18.0-before-2.8.0-denial-of-service-via-user-export-amplification

Questions about CVE-2026-134269

Is CVE-2026-134269 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: cve.now feed data

What does this mean?

An authenticated user can trigger a user export that exhausts server memory, causing the Vikunja instance to crash out of memory and go down for all users.

Source: github.com

Which versions are affected by CVE-2026-134269?

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

Source: cve.now feed data

Am I affected, and how do I check?

Vikunja versions 0.18.0 through 2.7.1 are affected; the facts name 2.8.0 as the patched version. To check a installation's version, look at the version shown by the Vikunja server or its release tag.

Source: github.com

How do I fix CVE-2026-134269?

Upgrade to Vikunja 2.8.0, which is the patched version named in the facts. No workaround is given in the checked facts.

Source: github.com

No corrections so far. Something wrong on this page? Report an error.