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

> Authenticated users can delete Kanban assignments and ordering in other projects by supplying mismatched view identifiers, leading to unauthorized data modification.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Aug 2026
- **Updated:** 1 Sep 2026
- **Also known as:** GHSA-gg93-x632-9ccv, GO-2026-6313

## What is CVE-2026-55065?

CVE-2026-55065 is a high-severity missing authorization vulnerability in go-vikunja vikunja, published on 28 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-285 (Improper Authorization)

## Which versions are affected by CVE-2026-55065?

3 open source packages ship an affected version, including code.vikunja.io/api.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `code.vikunja.io/api` | Go | From 0.24.6 | None |
| `code.vikunja.io/api` | Go | From 0.24.6 | 2.4.0 |
| `code.vikunja.io/api` | Go | From 0.24.6 | 2.4.0 |

## How do I fix CVE-2026-55065?

Upgrade code.vikunja.io/api to 2.4.0 or later.

## Is CVE-2026-55065 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55065 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-55065 and fix it if it is affected.

What it is: CVE-2026-55065 is a high-severity missing authorization vulnerability in go-vikunja vikunja, published on 28 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55065 exists.

Affected packages and fixed versions:
- code.vikunja.io/api (Go): affected from 0.24.6; no fix listed
- code.vikunja.io/api (Go): affected from 0.24.6; fixed in 2.4.0
- code.vikunja.io/api (Go): affected from 0.24.6; fixed in 2.4.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-55065/ (Markdown: https://insights.sbomify.com/CVE-2026-55065/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-55065
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-55065
- OSV: https://osv.dev/vulnerability/CVE-2026-55065

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-55065/
Summaries are generated and may contain mistakes; the official description above is the record.