CVE-2026-33700 Vikunja has a Link Share Delete IDOR — Missing Project Ownership Check Allows Cross-Project Link Share Deletion

What is CVE-2026-33700?

CVE-2026-33700 is a medium-severity missing authorization vulnerability in go-vikunja vikunja, published on 24 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.

Official description

Vikunja is an open-source self-hosted task management platform. Prior to version 2.2.1, the `DELETE /api/v1/projects/:project/shares/:share` endpoint does not verify that the link share belongs to the project specified in the URL. An attacker with admin access to any project can delete link shares from other projects by providing their own project ID combined with the target share ID. Version 2.2.1 patches the issue.

Weakness: CWE-639

Which versions are affected by CVE-2026-33700?

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

Products include Vikunja Vikunja.

How do I fix CVE-2026-33700?

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

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2026-33700 being exploited?

There is no known exploitation of CVE-2026-33700 in the wild and no public exploit code.

Other vulnerabilities in go-vikunja vikunja

• CVE-2026-28268 Vikunja Vulnerable to Account Takeover via Password Reset Token Reuse Critical 9.8
• CVE-2026-27575 Vijkunja has Weak Password Policy Combined with Persistent Sessions After Password Change Critical 9.1
• CVE-2026-25935 Vikunja Affected by XSS Via Task Preview High 8.6
• CVE-2026-35595 Vikunja Affected by Privilege Escalation via Project Reparenting High 8.3
• CVE-2026-33316 Vikunja’s Improper Access Control Enables Bypass of Administrator-Imposed Account Disablement High 8.1

Sources

• CVE record
• NVD
• OSV
• GitHub advisory
• How this page is made

Also known as GHSA-f95f-77jx-fcjc, GO-2026-4850.