---
id: "CVE-2026-123503"
page: "https://infrastack.ai/live/CVE-2026-123503"
kind: "vulnerability"
aliases: ["CVE-2026-123503"]
title: "Vikunja: users with project write access can delete buckets they should not"
severity: "medium"
cvss: 5.4
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["package", "project-management", "self-hosted", "vikunja"]
not_affected_if: ["managed-hosting", "read-only-projects", "single-user"]
published_at: "2026-11-08T02:16:38+00:00"
first_seen_at: "2026-11-08T02:21:08+00:00"
updated_at: "2026-11-08T02:25:16+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-123503", "first_seen_at": "2026-11-08T02:21:08+00:00"}]
exploit_sources: []
---

# Vikunja: users with project write access can delete buckets they should not

Link for people: https://infrastack.ai/live/CVE-2026-123503 (this .md is for agents)

Vikunja, a self-hosted task manager, checks bucket permissions against the wrong view, so a user with write access to a project can delete a bucket through another view's endpoint. This bypasses the rule that a project must keep at least one bucket and leaves task buckets and default/done references inconsistent.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed Vikunja version, for example with `vikunja version` or the image tag, and compare it with the fixed version below.
- Confirm whether untrusted or non-admin users have write access to shared projects.

## Fix

- Vikunja: move to `2.7.1` or later (the description says before 2.7.1 is affected).

## Timeline

- 2026-11-08T02:21:08+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-123503

## Documents

- [advisory] Vendor advisory: github.com https://github.com/go-vikunja/vikunja/security/advisories/GHSA-9xh7-5jg8-mf43
- [advisory] Third-party advisory: www.vulncheck.com https://www.vulncheck.com/advisories/vikunja-before-2.7.1-improper-authorization-in-kanban-bucket-deletion

## From the sources

Vikunja before 2.7.1 contains an improper authorization vulnerability in canDoBucket that allows users with project write access to delete buckets via a mismatched view ID. Attackers can request deletion through another view's bucket endpoint to bypass the last-bucket rule, leaving dangling default/done bucket references and inconsistent task buckets.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_