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-35602: CWE-770: Allocation of Resources Without Limits or Throttling in go-vikunja vikunja

0
Medium
VulnerabilityCVE-2026-35602cvecve-2026-35602cwe-770
Published: Fri Apr 10 2026 (04/10/2026, 16:10:39 UTC)
Source: CVE Database V5
Vendor/Project: go-vikunja
Product: vikunja

Description

Vikunja is an open-source self-hosted task management platform. Prior to 2.3.0, the Vikunja file import endpoint uses the attacker-controlled Size field from the JSON metadata inside the import zip instead of the actual decompressed file content length for the file size enforcement check. By setting Size to 0 in the JSON while including large compressed file entries in the zip, an attacker bypasses the configured maximum file size limit. This vulnerability is fixed in 2.3.0.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 04/18/2026, 14:22:48 UTC

Technical Analysis

CVE-2026-35602 is a resource allocation vulnerability (CWE-770) in the open-source task management platform Vikunja before version 2.3.0. The file import endpoint relies on the attacker-controlled Size field from JSON metadata inside import zip files to enforce file size limits rather than the actual decompressed file content length. By setting Size to 0 while including large compressed files, an attacker can bypass the maximum file size restriction, leading to uncontrolled resource consumption. This vulnerability has a CVSS 3.1 base score of 5.4 (medium severity) and does not affect confidentiality but impacts integrity and availability. The vulnerability is resolved in Vikunja 2.3.0.

Potential Impact

Exploitation allows attackers with limited privileges to bypass file size restrictions during import, potentially causing excessive resource consumption and denial of service. There is no direct confidentiality impact, but integrity and availability can be affected due to resource exhaustion.

Mitigation Recommendations

Upgrade Vikunja to version 2.3.0 or later, where this vulnerability is fixed. Since the vendor advisory confirms the issue is resolved in 2.3.0, applying this official fix is the recommended remediation. No additional mitigations are specified.

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-04-03T21:25:12.162Z
Cvss Version
3.1
State
PUBLISHED
Remediation Level
null

Threat ID: 69d9d9751cc7ad14da3f8740

Added to database: 4/11/2026, 5:17:41 AM

Last enriched: 4/18/2026, 2:22:48 PM

Last updated: 5/10/2026, 1:33:50 PM

Views: 84

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