# CVE-2026-33312: Read-only Vikunja users can delete project background images via broken object-level authorization

> Read-only users can delete project background images due to incorrect permission checks, allowing unauthorized data modification.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **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:** 20 Mar 2026
- **Updated:** 20 Mar 2026
- **Also known as:** GHSA-564f-wx8x-878h, GO-2026-4795

## What is CVE-2026-33312?

CVE-2026-33312 is a medium-severity missing authorization vulnerability in go-vikunja vikunja, published on 20 Mar 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. Starting in version 0.20.2 and prior to version 2.2.0, the `DELETE /api/v1/projects/:project/background` endpoint checks `CanRead` permission instead of `CanUpdate`, allowing any user with read-only access to a project to permanently delete its background image. Version 2.2.0 fixes the issue.

Weakness: CWE-863 (Incorrect Authorization)

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

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


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

Products: Vikunja Vikunja.

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

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

## Is CVE-2026-33312 being exploited?

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

## Other vulnerabilities in go-vikunja vikunja

- [CVE-2026-28268](https://insights.sbomify.com/CVE-2026-28268/): Vikunja Vulnerable to Account Takeover via Password Reset Token Reuse (critical 9.8)
- [CVE-2026-27575](https://insights.sbomify.com/CVE-2026-27575/): Vijkunja has Weak Password Policy Combined with Persistent Sessions After Password Change (critical 9.1)
- [CVE-2026-25935](https://insights.sbomify.com/CVE-2026-25935/): Vikunja Affected by XSS Via Task Preview (high 8.6)
- [CVE-2026-35595](https://insights.sbomify.com/CVE-2026-35595/): Vikunja Affected by Privilege Escalation via Project Reparenting (high 8.3)
- [CVE-2026-33316](https://insights.sbomify.com/CVE-2026-33316/): Vikunja’s Improper Access Control Enables Bypass of Administrator-Imposed Account Disablement (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-33312 is a medium-severity missing authorization vulnerability in go-vikunja vikunja, published on 20 Mar 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-33312 exists.

Affected packages and fixed versions:
- code.vikunja.io/api (Go): affected from 0.20.2; no fix listed
- code.vikunja.io/api (Go): affected from 0.20.2; fixed in 2.2.0
- code.vikunja.io/api (Go): affected from 0.20.2; fixed in 2.2.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-33312/ (Markdown: https://insights.sbomify.com/CVE-2026-33312/index.md)
```

## Sources

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

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