CVE-2026-134269 in Vikunja
Summary
by MITRE • 11/21/2026
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.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Analysis
by VulDB Data Team • 11/21/2026
The vulnerability identified in Vikunja versions prior to 2.8.0 represents a significant resource amplification flaw located within the application's data export functionality, specifically in the pkg/models/export.go module. This issue stems from inefficient handling of relational data during the serialization process for user exports. When an authenticated user initiates an export operation, the system traverses relationships between tasks to compile comprehensive project or user data. The core technical defect lies in the failure to implement depth limits or cycle detection mechanisms when resolving these nested relationships. Consequently, if a malicious actor constructs a scenario where numerous tasks are linked to a single task containing a large description field, the export engine attempts to recursively process this structure without adequate constraints. This leads to an exponential increase in memory consumption as the system tries to materialize every related entity and its associated metadata into memory simultaneously.
From a technical perspective, this flaw is classified under CWE-400, which denotes uncontrolled resource consumption. The attack vector relies on authenticated access, meaning that any valid user account can exploit this condition without requiring privilege escalation or external network exposure beyond the application interface itself. By carefully crafting task relationships and descriptions, an attacker can trigger a denial of service against the entire server infrastructure rather than just their own session. This is because the memory exhaustion occurs at the process level, causing the Vikunja backend to crash due to out-of-memory errors. Such crashes disrupt availability for all concurrent users, effectively halting productivity and potentially leading to data loss if unsaved work is lost during the service restart or failure event.
The operational impact of this vulnerability extends beyond simple downtime. In a multi-tenant environment or even within a single organization using Vikunja as a central task management tool, an out-of-memory crash can corrupt database connections, interrupt ongoing transactions, and degrade system stability significantly. Attackers may leverage this capability to conduct persistent denial-of-service attacks by repeatedly triggering the export function with optimized malicious payloads. This aligns with ATT&CK technique T1498, Network Denial of Service, specifically through resource exhaustion via application layer abuse. The ability to crash all users highlights a critical gap in input validation and resource management within the export module's design philosophy, which prioritizes completeness over performance safeguards for deeply nested relational data.
Mitigation strategies must focus on immediate patching and architectural hardening. Organizations running Vikunja versions from 0.18.0 up to but not including 2.8.0 should upgrade to version 2.8.0 or later, where the developers have addressed this resource amplification issue by implementing proper limits on relationship traversal depth and optimizing memory usage during export operations. In environments where immediate patching is not feasible, administrators can implement temporary controls such as rate limiting on export endpoints to prevent rapid successive requests that might exacerbate memory pressure. Additionally, configuring application-level memory limits or deploying reverse proxies with request size restrictions can help mitigate the severity of resource exhaustion attacks until a permanent fix is applied. Regular security audits focusing on recursive data processing functions are recommended to identify similar patterns in other modules before they become exploitable vulnerabilities.