CVE-2026-55067

Vikunja: Authenticated cross-tenant kanban-bucket relocation via `project_view_id` mass-assignment

Published Aug 28, 2026 CVSS 3.1 · 5 Medium EPSS < 1% KEV · Not listed
Description
Vikunja is an open-source self-hosted task management platform. Prior to 2.4.0, POST /api/v1/projects/{project}/views/{view}/buckets/{bucket} allows the request body project_view_id value to be mass assigned by Bucket.Update in pkg/models/kanban.go. The permission check validates that the bucket currently belongs to the URL project and view but does not validate the body selected destination view, allowing any authenticated user to relocate an attacker-owned bucket into another tenant’s Kanban view. The injected bucket retains attacker-controlled content and ownership, enabling cross-tenant defacement. This issue is fixed in version 2.4.0.

Analysis

AI-generated

Technical impact

Vikunja is a self‑hosted task‑management platform. In versions prior to 2.4.0, the API endpoint POST /api/v1/projects/{project}/views/{view}/buckets/{bucket} accepted a body parameter project_view_id that was mass assigned without validating the intended destination view. This allowed an authenticated user to move a bucket they owned into any other tenant’s Kanban view. The bucket—and the data it contains—was then retained with the attacker’s ownership, effectively enabling cross‑tenant defacement. The flaw is a classic example of improper input validation (CWE‑639).

Affected Systems

All installations of the Vikunja platform produced by go‑vikunja:vikunja that run a version earlier than 2.4.0 are affected. The vulnerability applies to the API endpoint handling bucket relocations within the Kanban module.

Risk and Exploitability

The vulnerability’s CVSS score of 5 indicates moderate severity, and its EPSS score is not available. It is not listed in the CISA KEV catalogue. Exploitation requires the attacker to be an authenticated user with the ability to create or move buckets. Once the user has those credentials, they can relocate a bucket into another tenant’s view, which can lead to defacement and potential data compromise. The attack vector is likely internal or via compromised legitimate credentials.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Vikunja to version 2.4.0 or later, which removes the mass‑assignment flaw.
  • Update any affected bucket permissions to ensure they belong only to the intended tenant after the upgrade.
  • If an upgrade is not immediately possible, restrict the POST API for bucket relocation to administrators and monitor activity for unauthorized bucket movements.

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

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-569v-q83c-3j3g Vikunja vulnerable to authenticated cross-tenant kanban-bucket relocation via `project_view_id` mass-assignment
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. Prior to 2.4.0, POST /api/v1/projects/{project}/views/{view}/buckets/{bucket} allows the request body project_view_id value to be mass assigned by Bucket.Update in pkg/models/kanban.go. The permission check validates that the bucket currently belongs to the URL project and view but does not validate the body selected destination view, allowing any authenticated user to relocate an attacker-owned bucket into another tenant’s Kanban view. The injected bucket retains attacker-controlled content and ownership, enabling cross-tenant defacement. This issue is fixed in version 2.4.0.
Title Vikunja: Authenticated cross-tenant kanban-bucket relocation via `project_view_id` mass-assignment
Weaknesses CWE-639
References
Metrics cvssV3_1

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

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key

Sources

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