CVE-2026-55065

Vikunja: Improper Authorization and Authorization Bypass Through User-Controlled Key in code.vikunja.io/api

Published Aug 28, 2026 CVSS 3.1 · 8.1 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The vulnerability in Vikunja allows an authenticated user to delete a view in another project by supplying an arbitrary view identifier while only authorizing against the supplied project identifier. ProjectView.CanDelete fails to verify that the view belongs to the target project, and ProjectView.Delete continues even when no rows are affected for the scoped delete. This permits cross‑tenant destruction of Kanban assignments and ordering without affecting the view or tasks themselves. The weakness is reflected in the CWE-285 (Improper Authorization) and CWE-639 (Authorization Bypass Through User‑Controlled Key) categories, indicating that the integrity of project data can be compromised.

Affected Systems

Vikunja, the open‑source self‑hosted task management platform from go‑vikunja, is affected in all releases from version 0.24.6 through, but not including, 2.4.0. Users running any of these versions should treat the system as vulnerable until the fix in 2.4.0 or a newer release is applied.

Risk and Exploitability

The CVSS score of 8.1 demonstrates a high severity level, meaning the vulnerability can cause significant damage if exploited. The EPSS score is not available, so exploitation probability is unknown, but the lack of any listing in the CISA KEV catalog suggests no confirmed active exploitation. The attack vector requires the attacker to be authenticated and to have permissions to delete views for the target project, yet the validation logic is bypassed. An attacker can therefore manipulate the order and assignments of tasks in another project, potentially disrupting project workflows and causing confusion among users.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Vikunja to version 2.4.0 or later immediately to apply the patched permissions logic.
  • Until the upgrade is completed, restrict the DELETE /api/v1/projects/:project/views/:view API to users with mandatory project‑owner or admin roles and enforce a check that the provided view_id actually belongs to the parent project before performing the delete operation.
  • Audit event logs for unexpected view deletions across projects and restore any affected Kanban ordering or task assignments if discovered.

Generated by OpenCVE AI on August 28, 2026 at 20:58 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-gg93-x632-9ccv Vikunja vulnerable to Improper Authorization and Authorization Bypass Through User-Controlled Key
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Go-vikunja
Go-vikunja vikunja
Vendors & Products Go-vikunja
Go-vikunja vikunja
Type Values Removed Values Added
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.
Title Vikunja: Improper Authorization and Authorization Bypass Through User-Controlled Key in code.vikunja.io/api
Weaknesses CWE-285
CWE-639
References
Metrics cvssV3_1

{'score': 8.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H'}

Weaknesses
  • CWE-285

    Improper Authorization

  • CWE-639

    Authorization Bypass Through User-Controlled Key

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Sep 1, 2026, 1:46 AM
Reserved
Jun 16, 2026, 2:33 PM
Status
Deferred
Published
Aug 28, 2026, 8:18 PM
Modified
Sep 9, 2026, 9:09 PM