CVE-2026-134265 in Vikunja
Summary
by MITRE • 11/21/2026
Vikunja from 2.4.0 before 2.8.0 contains a denial of service vulnerability in the richtext converter that allows authenticated project writers to exhaust server memory and CPU by storing tables with unbounded rowspan and colspan values. Any project reader or CalDAV client can trigger the expansion through markdown task reads, CalDAV GETs, or the frontend editor, producing 100 MB responses from a 64-byte description.
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 exhaustion flaw within its richtext conversion subsystem. This issue specifically affects authenticated users who possess project writer privileges, allowing them to craft malicious input that triggers disproportionate server-side processing and memory allocation. The core of the problem lies in how the application handles HTML table attributes during the rendering process. Specifically, when a user stores a task description containing an HTML table with unbounded or excessively large rowspan and colspan values, the underlying conversion logic fails to enforce reasonable limits on these dimensions. This lack of input validation allows attackers to define tables that are logically impossible or computationally expensive to render correctly by standard web browsers or document processors.
From a technical perspective, this flaw is classified as an Improper Limitation of a Resource Exhaustion vulnerability, aligning with CWE-400 in the Common Weakness Enumeration taxonomy. The mechanism involves the server attempting to expand these malformed table structures into their full rendered form during read operations. When a project reader accesses such a task or when a CalDAV client performs a GET request for calendar events containing this data, the application's frontend editor and backend converters attempt to process the unbounded values. This results in the generation of disproportionately large response payloads; reports indicate that a mere 64-byte input description can trigger the creation of responses exceeding one hundred megabytes. The server must allocate significant memory buffers to construct these massive structures and consume substantial CPU cycles during the conversion and serialization processes, leading to severe performance degradation for all users sharing the affected project or instance.
The operational impact of this vulnerability is primarily a Denial of Service against both the application infrastructure and legitimate end-users. By exploiting this flaw, an attacker can systematically exhaust available server memory and processing power, potentially causing service outages for other tenants in multi-tenant deployments or crashing individual user sessions. The attack vector is particularly insidious because it leverages standard interaction patterns such as reading tasks via markdown task lists or retrieving calendar data through CalDAV protocols. This means that the vulnerability can be triggered not only by direct API calls but also through routine client-side interactions, making detection and prevention more challenging without strict input sanitization at the point of entry. The ability to generate massive responses from minimal inputs creates a classic amplification effect, where small malicious payloads result in large resource consumption events.
To mitigate this risk, immediate action is required by upgrading Vikunja to version 2.8.0 or later, which addresses these input validation gaps. In the interim, administrators should implement strict rate limiting and request size restrictions at the reverse proxy or web server level to prevent excessively large responses from being served. Additionally, deploying a Web Application Firewall with rules designed to detect anomalous HTML table structures in POST bodies can provide an additional layer of defense against exploitation attempts. Security teams should also monitor for unusual spikes in memory usage associated with task rendering services and review access logs for repeated requests involving rich text fields containing complex table markup. This incident underscores the importance of enforcing strict bounds on all user-controlled input parameters that influence dynamic content generation, particularly within collaborative platforms where data integrity and availability are paramount. The vulnerability highlights a common pattern in web applications where convenience features like richtext editors introduce complexity that can be exploited if proper sanitization and validation logic is not rigorously applied to structural elements like tables.