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-35599: CWE-407: Inefficient Algorithmic Complexity in go-vikunja vikunja

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

Description

Vikunja versions prior to 2. 3. 0 contain an inefficient algorithmic complexity vulnerability in the addRepeatIntervalToTime function. This function uses a loop that advances a date by the task's RepeatAfter interval until it exceeds the current time. An attacker can exploit this by creating a repeating task with a 1-second interval and a due date far in the past, causing billions of loop iterations. This results in high CPU consumption and prolonged database connection usage per request. The vulnerability is fixed in version 2. 3. 0.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 04/10/2026, 18:51:22 UTC

Technical Analysis

The vulnerability in go-vikunja's vikunja product (CVE-2026-35599) is due to inefficient algorithmic complexity (CWE-407) in the addRepeatIntervalToTime function. The function iterates in an O(n) loop, incrementing a date by the RepeatAfter interval until it surpasses the current time. When exploited by setting a 1-second repeat interval with a due date far in the past, this causes excessive loop iterations, leading to significant CPU resource consumption and holding database connections for extended periods. This can degrade service availability. The issue is resolved in version 2.3.0.

Potential Impact

The vulnerability causes high CPU usage and prolonged database connection occupancy, potentially leading to denial of service conditions by exhausting server resources. There is no impact on confidentiality or integrity. The CVSS score is 6.5 (medium severity) reflecting the availability impact. No known exploits are reported in the wild.

Mitigation Recommendations

Upgrade to vikunja version 2.3.0 or later, where this vulnerability is fixed. Since no official patch link or advisory is provided, users should verify the version upgrade from the vendor's official sources. Patch status is not explicitly confirmed beyond the version fix note, so check vendor advisories for current remediation guidance.

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: 69d943121cc7ad14dadcb1b3

Added to database: 4/10/2026, 6:36:02 PM

Last enriched: 4/10/2026, 6:51:22 PM

Last updated: 4/10/2026, 9:14:42 PM

Views: 4

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