Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-33474: CWE-400: Uncontrolled Resource Consumption in go-vikunja vikunja

0
Medium
VulnerabilityCVE-2026-33474cvecve-2026-33474cwe-400
Published: Tue Mar 24 2026 (03/24/2026, 15:21:19 UTC)
Source: CVE Database V5
Vendor/Project: go-vikunja
Product: vikunja

Description

CVE-2026-33474 is a medium severity vulnerability in the open-source task management platform Vikunja, affecting versions from 1. 0. 0-rc0 up to but not including 2. 2. 0. The flaw arises from unbounded image decoding and resizing during preview generation, allowing attackers to submit highly compressed images with extremely large dimensions. This leads to uncontrolled resource consumption, exhausting CPU and memory, and causing denial of service. Exploitation requires low privileges but no user interaction and can be performed remotely over the network. The vulnerability impacts availability but does not affect confidentiality or integrity. Version 2.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/24/2026, 16:05:53 UTC

Technical Analysis

CVE-2026-33474 is a resource exhaustion vulnerability classified under CWE-400, found in the go-vikunja Vikunja platform, an open-source self-hosted task management system. The vulnerability exists in versions starting from 1.0.0-rc0 up to but not including 2.2.0. It stems from the way Vikunja handles image preview generation: the system performs image decoding and resizing without bounding the resource consumption. An attacker can craft a highly compressed image file that decompresses into an extremely large image dimension. When Vikunja processes this image for preview, it consumes excessive CPU cycles and memory, leading to potential denial of service (DoS) by exhausting server resources. The attack vector is network-based and requires low privileges (PR:L), with no user interaction needed (UI:N). The vulnerability does not compromise confidentiality or integrity but severely impacts availability. The CVSS v3.1 score is 6.5 (medium severity), reflecting the ease of exploitation and the significant impact on availability. The issue was publicly disclosed on March 24, 2026, and fixed in version 2.2.0. No known exploits are currently reported in the wild. The vulnerability highlights the importance of input validation and resource management in image processing components of web applications.

Potential Impact

The primary impact of CVE-2026-33474 is denial of service through resource exhaustion, which can disrupt the availability of Vikunja services. Organizations relying on Vikunja for task management may experience service outages or degraded performance, affecting productivity and operational continuity. Since Vikunja is often self-hosted, smaller organizations or teams without robust infrastructure may be particularly vulnerable to such disruptions. The vulnerability does not expose sensitive data or allow unauthorized data modification, limiting its impact to availability. However, prolonged or repeated exploitation could lead to significant operational downtime, increased incident response costs, and potential reputational damage. In environments where Vikunja is integrated into larger workflows or automation pipelines, this DoS could cascade, affecting dependent systems and processes.

Mitigation Recommendations

To mitigate CVE-2026-33474, organizations should upgrade Vikunja installations to version 2.2.0 or later, where the vulnerability is patched. Until upgrading is possible, administrators should implement resource limits on image processing tasks, such as restricting maximum image dimensions, file size, and processing time. Deploying rate limiting and input validation on image uploads can help prevent maliciously crafted images from being processed. Monitoring system resource usage and setting alerts for unusual CPU or memory spikes related to image handling can provide early detection of exploitation attempts. Additionally, isolating the image processing component in a sandboxed environment or container with strict resource quotas can limit the impact of any attack. Regularly reviewing and updating dependencies and applying security patches promptly is critical for maintaining a secure environment.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-03-20T16:16:48.969Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69c2b1b2f4197a8e3b48d1b2

Added to database: 3/24/2026, 3:45:54 PM

Last enriched: 3/24/2026, 4:05:53 PM

Last updated: 3/24/2026, 6:19:27 PM

Views: 3

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses