CVE-2026-134268
Deferred Deferred - Pending Action

Resource Exhaustion in Vikunja via Project Position Manipulation

Vulnerability report for CVE-2026-134268, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-21

Last updated on: 2026-11-21

Assigner: VulnCheck

Description

Vikunja from 0.21.0 before 2.8.0 contains a resource exhaustion vulnerability that allows authenticated users to trigger instance-wide database writes by setting a project position below 0.1. Attackers can repeatedly send PUT requests to /api/v2/projects/{id} so recalculateProjectPositions updates every user's root projects, holding SQLite's write lock and degrading availability.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-21
Last Modified
2026-11-21
Generated
2026-11-21
AI Q&A
2026-11-21
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
vikunja vikunja From 0.21.0 (inc) to 2.8.0 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-400 The product does not properly control the allocation and maintenance of a limited resource.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in Vikunja (CVE-2026-134268) is a resource exhaustion issue where authenticated users can trigger excessive database writes. By setting a project position below 0.1 and sending repeated PUT requests to /api/v2/projects/{id}, the system recalculates positions for all root projects across every user. This causes SQLite to hold its global write lock continuously, degrading performance or causing deadlocks.

Detection Guidance

Monitor for repeated PUT requests to /api/v2/projects/{id} with position values below 0.1. Check for high database write activity or SQLite lock contention. Use network traffic analysis tools to detect unusual API call patterns targeting project endpoints.

Impact Analysis

If exploited, this vulnerability can lead to severe performance degradation or complete unavailability of the Vikunja instance. Database operations slow down or fail due to locked resources, affecting all users. Attackers could repeatedly trigger this to cause a Denial of Service (DoS), making the system unusable.

Compliance Impact

This vulnerability can lead to system unavailability due to database write lock contention, which may violate availability requirements in GDPR (Article 32) and HIPAA (Security Rule Β§164.308(a)(7)). Persistent DoS conditions could also impact data integrity and access controls.

Mitigation Strategies
  • Upgrade Vikunja to version 2.8.0 or later to apply the official patch.
  • Restrict PUT requests to /api/v2/projects/{id} by implementing rate limiting or input validation to block position values below 0.1.
  • Review and restrict database write permissions to minimize impact during recalculation operations.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-134268. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...