CVE-2026-134271 in Vikunja
Summary
by MITRE • 11/21/2026
Vikunja from 1.0.0 before 2.8.0 contains a memory exhaustion vulnerability that allows authenticated users to crash the server by uploading extreme-width images as task attachments. Attackers can request the attachment preview endpoint so Lanczos resampling allocates width-proportional weight tables, OOM-killing the process repeatedly with sub-megabyte PNGs.
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 vulnerability identified in Vikunja versions prior to 2.8.0 represents a significant resource exhaustion flaw rooted in improper handling of image processing operations during attachment preview generation. This issue specifically affects authenticated users who possess the ability to upload files as task attachments within the application. The core technical deficiency lies in how the backend processes these images when generating previews, particularly regarding dimension validation and memory allocation strategies for resampling algorithms.
At a technical level, the flaw is triggered when an attacker uploads an image with extreme width dimensions but relatively small file size, such as sub-megabyte PNG files that utilize specific compression or structural properties to maintain low disk footprint while maintaining large pixel counts in one axis. When the system attempts to generate a preview for this attachment, it invokes Lanczos resampling, a high-quality interpolation method used for image resizing and filtering. The implementation allocates weight tables proportional to the width of the source image without enforcing reasonable upper bounds on these dimensions or accounting for the resulting memory footprint required by the algorithm's internal data structures.
This lack of input validation allows an attacker to craft images that appear benign in terms of file size but require massive amounts of RAM during processing. The Lanczos resampling process creates weight tables whose memory consumption scales linearly with image width, leading to rapid allocation of system resources. Since there is no cap on the maximum allowable width for preview generation, repeated requests from an authenticated user can exhaust available server memory. This results in Out-of-Memory conditions that cause the application process to be terminated by the operating system's OOM killer mechanism.
The operational impact of this vulnerability includes denial of service against the Vikunja instance and potential instability for other users sharing the same resources if deployed in a multi-tenant or shared hosting environment. The repeated crashing of the server process disrupts availability, requiring manual intervention to restart services. Furthermore, because the attack requires authentication, it is classified as an insider threat vector rather than an unauthenticated remote exploit, yet it remains critical due to the ease with which authenticated users can degrade service reliability through simple file uploads and preview requests.
From a classification perspective, this vulnerability aligns with CWE-400: Uncontrolled Resource Consumption, specifically manifesting as memory exhaustion. It also relates to CWE-789: Memory Allocation with Excessive Size Value, where the system allocates more memory than intended or safe based on unvalidated input dimensions. In terms of attack patterns, this behavior is consistent with ATT&CK technique T1496: Resource Hijacking, as it involves consuming computational resources to disrupt service availability rather than compromising confidentiality or integrity directly.
Mitigation strategies should focus on implementing strict validation rules for image dimensions prior to processing. Administrators and developers must enforce maximum width and height limits that are reasonable for preview generation purposes, ensuring that the resulting memory allocation remains within safe bounds regardless of input file size. Additionally, integrating resource monitoring and rate limiting can help detect and prevent abuse patterns associated with repeated large-scale requests. Upgrading to Vikunja version 2.8.0 or later resolves this issue by addressing the underlying logic flaws in image processing pipelines.