CVE-2026-134270 in Vikunja
Summary
by MITRE • 11/21/2026
Vikunja from 0.19.0 before 2.8.0 contains a denial of service vulnerability that allows authenticated CalDAV users to exhaust server CPU by uploading VTODO properties with many parameters. Attackers can PUT an iCalendar body with thousands of parameters on one line to any valid project ID, triggering superlinear parsing before permission checks.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Analysis
by VulDB Data Team • 11/21/2026
The identified security flaw resides within the Vikunja application, specifically affecting versions ranging from 0.19.0 up to but not including version 2.8.0. This vulnerability is classified as a denial of service condition that targets authenticated CalDAV users. The core issue stems from an inefficient parsing mechanism for iCalendar data structures, particularly when handling VTODO properties. When an attacker submits a PUT request containing an iCalendar body with thousands of parameters condensed onto a single line and associated with any valid project ID, the server initiates a superlinear parsing process before executing permission checks. This architectural decision to parse input prior to validating access rights creates a significant resource exhaustion vector that can be exploited by low-privilege users to degrade or halt service availability for all other system participants.
From a technical perspective, the vulnerability exploits the order of operations in request handling within the CalDAV interface. By injecting malformed iCalendar data characterized by an excessive number of parameters on a single line, the attacker forces the server's parser into a computational loop that scales poorly with input size. This superlinear complexity means that as the number of parameters increases, the CPU time required to process them grows disproportionately rather than linearly. Because this parsing occurs before authentication and authorization checks are fully completed or applied to the specific resource context, even users with minimal privileges can trigger high-cost operations. The lack of early validation allows malicious payloads to consume significant server resources during the initial ingestion phase, leading to CPU exhaustion that impacts the stability of the entire application instance.
The operational impact of this vulnerability is severe for organizations relying on Vikunja for task and calendar management services. An attacker with valid credentials can execute a sustained denial-of-service attack by repeatedly sending these optimized payloads. This activity consumes server processing power, potentially causing latency spikes, request timeouts, or complete unavailability of the service to legitimate users. In cloud-hosted environments, this could also lead to increased infrastructure costs due to excessive CPU usage metrics being triggered automatically. The ability for authenticated users to disrupt service highlights a critical gap in input validation strategies and resource management protocols within the application's CalDAV implementation.
To mitigate this risk, immediate action is required by upgrading Vikunja to version 2.8.0 or later, where these parsing inefficiencies have been addressed. In environments where an upgrade is not immediately feasible, administrators should implement network-level controls such as rate limiting on CalDAV endpoints and restrict the maximum size of incoming HTTP requests containing iCalendar data. Additionally, deploying a Web Application Firewall with rules designed to detect abnormally long lines or excessive parameter counts in calendar-related payloads can provide a layer of defense against exploitation attempts. It is also advisable to review authentication logs for patterns indicative of repeated PUT operations targeting various project IDs with unusually large payload sizes.
This vulnerability aligns with CWE-787, which describes out-of-bounds write scenarios that can lead to memory corruption or resource exhaustion, although in this specific case the primary manifestation is computational rather than memory-based. It also relates closely to CWE-400, concerning uncontrolled resource consumption, where an actor can cause a system to exhaust available resources such as CPU cycles or memory. From an offensive security perspective, particularly within the MITRE ATT&CK framework, this behavior maps to T1496, Resource Hijacking, specifically under the subtechnique of Denial of Service via computational exhaustion. Understanding these classifications helps in developing more robust detection rules and long-term architectural improvements to prevent similar resource abuse vectors in future software updates.