CVE-2026-55065

Received Received - Intake

Authenticated Project View Deletion in Vikunja

Publication date: 2026-08-28

Last updated on: 2026-08-28

Assigner: GitHub, Inc.

Description

Vikunja is an open-source self-hosted task management platform. From 0.24.6 until 2.4.0, DELETE /api/v1/projects/:project/views/:view permits an authenticated user to supply a view identifier from another project while authorizing only against an attacker-controlled project identifier. ProjectView.CanDelete in pkg/models/project_view_permissions.go does not establish that the view belongs to the path project, and ProjectView.Delete in pkg/models/project_view.go continues after the scoped project_views delete affects no rows. Its subsequent deletes select task_buckets and task_positions only by project_view_id, allowing cross-tenant destruction of Kanban assignments and ordering while leaving the victim view and tasks intact. This issue is fixed in version 2.4.0.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-08-28

Last Modified

2026-08-28

Generated

2026-08-29

AI Q&A

2026-08-29

EPSS Evaluated

N/A

NVD

CVE-2026-55065

EUVD

EUVD-2026-67832

Affected Vendors & Products

Vendor	Product	Version / Range
vikunja	vikunja	From 0.24.6 (exc) to 2.4.0 (inc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-639	The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
CWE-285	The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.

Attack-Flow Graph

Executive Summary

CVE-2026-55065 is an improper authorization vulnerability in Vikunja, an open-source task management platform. It allows authenticated users to delete Kanban task assignments and ordering data from any project view by exploiting a flaw in the ProjectView.Delete method. The issue occurs because cascading deletes for task_buckets and task_positions do not properly scope the project ID, only filtering by view ID. Attackers can target any view by knowing its ID, which is often predictable.

Detection Guidance

To detect this vulnerability, check Vikunja server logs for DELETE requests to /api/v1/projects/:project/views/:view with 200 OK responses where the project ID in the path does not match the view's project. Monitor for unexpected Kanban layout or task ordering corruption in projects.

Impact Analysis

This vulnerability can lead to permanent loss of Kanban layout and task ordering data across projects. Attackers can disrupt workflows by deleting task assignments and ordering without needing elevated privileges beyond basic authentication. Recovery requires restoring from backups as there is no in-application recovery path.

Mitigation Strategies

Immediately upgrade Vikunja to version 2.4.0 or later. If upgrading is not possible, restrict access to the DELETE /api/v1/projects/:project/views/:view endpoint via network controls or disable affected functionality until patched.

Hi! I’m here to help you understand CVE-2026-55065. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70