CVE-2026-134275 in Vikunja
Summary
by MITRE • 11/21/2026
Vikunja from 0.8.0 before 2.8.0 contains a denial of service vulnerability that allows authenticated project readers to amplify response size by repeating requested properties in CalDAV PROPFIND requests. Attackers can send PROPFIND requests to the dav projects endpoint with hundreds of duplicate calendar-data properties to exhaust server memory, CPU, and bandwidth.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Analysis
by VulDB Data Team • 11/21/2026
The identified security flaw resides within Vikunja versions ranging from 0.8.0 up to but not including 2.8.0, specifically affecting the CalDAV protocol implementation used for project data synchronization. This vulnerability is classified as a denial of service issue that exploits the server's handling of PROPFIND requests sent by authenticated users with reader-level permissions on projects. The core technical deficiency lies in the application's failure to validate or limit the number of properties requested within a single CalDAV query, allowing an attacker to artificially inflate the size and complexity of the response payload through property repetition.
From a technical perspective, the vulnerability stems from how the server processes XML-based PROPFIND requests over the WebDAV protocol extension known as CalDAV. When a client sends a request containing hundreds or thousands of duplicate calendar-data properties, the backend logic attempts to resolve and serialize each requested field individually without applying any rate limiting or payload size constraints. This lack of input validation results in excessive memory allocation for object instantiation and significant CPU cycles dedicated to data serialization and formatting. The server essentially enters an inefficient processing loop where it generates a disproportionately large response body relative to the actual unique information required, leading to resource exhaustion on the host system.
The operational impact of this vulnerability is severe for infrastructure stability. By repeatedly sending these amplified requests, an authenticated attacker can consume substantial amounts of server memory and central processing unit resources. This consumption degrades performance for legitimate users sharing the same environment or causes complete service unavailability if the resource limits are reached. Furthermore, the generation of large response payloads consumes significant network bandwidth, potentially saturating outgoing connections and affecting other services hosted on the same network segment. Since authentication is required to exploit this flaw, it represents a threat primarily from insider actors or compromised user accounts rather than anonymous external attackers.
This vulnerability aligns with CWE-400, which describes uncontrolled resource consumption, as well as CWE-770, specifically allocation of resources without limits or thresholds in the context of denial of service attacks. In terms of offensive security frameworks such as MITRE ATT&CK, this behavior corresponds to techniques involving resource exhaustion and potentially impacts availability through application layer flooding. The attack vector is classified as network-accessible with low complexity but requires authentication, placing it within the privilege escalation or abuse of existing access categories depending on how the compromised account was obtained.
To mitigate this risk, immediate updates to Vikunja version 2.8.0 or later are strongly recommended by the vendor, as these versions include fixes for the property handling logic in the CalDAV endpoint. In environments where patching is not immediately feasible, administrators should implement network-level controls such as Web Application Firewalls that inspect and limit the size of incoming XML payloads or restrict the number of properties allowed per PROPFIND request. Additionally, configuring server-side timeouts and memory limits for HTTP handlers can help contain the impact of such requests by terminating connections that exceed defined resource thresholds before they cause systemic failure. Regular auditing of CalDAV client configurations to ensure compliance with standard property sets can also reduce the likelihood of accidental or malicious abuse of this endpoint.