# Vikunja has an incomplete fix for CVE-2026-35595: Write-only user can detach shared project from parent hierarchy via parent_project_id=0

Advisory record · `GHSA-44v6-7fxq-vgf4`

- **Identifiers:** `GHSA-44v6-7fxq-vgf4` · `CVE-2026-55064` · `GO-2026-6306`
- **State:** Confirmed
- **Severity:** CVSS 4.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-862](https://cwe.mitre.org/data/definitions/862.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 28 Aug 2026
- **Updated:** 2 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 28 Aug 2026, 16:39 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `code.vikunja.io/api` (Go): affected `>=2.3.0, <2.4.0`; fixed in `2.4.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Vikunja versions 2.3.0 up to (but not including) 2.4.0 are affected. A user with Write permission on a shared child project, but not Admin, can detach that project from its parent by sending a project update with parent_project_id set to 0. This bypasses the Admin requirement that was meant to block re-parenting, and can disrupt permission inheritance for other collaborators. Upgrade to Vikunja 2.4.0 or later.

Written 6 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 4.3 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0037, the 30th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:47 UTC: First seen by agentprime
- 31 Oct 2026, 14:47 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-44v6-7fxq-vgf4)

## Sources

- [GitHub Advisory Database: GHSA-44v6-7fxq-vgf4](https://github.com/advisories/GHSA-44v6-7fxq-vgf4)
- [OSV: GHSA-44v6-7fxq-vgf4](https://osv.dev/vulnerability/GHSA-44v6-7fxq-vgf4)
- <https://github.com/go-vikunja/vikunja/security/advisories/GHSA-44v6-7fxq-vgf4>
- <https://github.com/go-vikunja/vikunja>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-44v6-7fxq-vgf4>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-44v6-7fxq-vgf4/>. Everything for agents: <https://agentprime.io/llms.txt>.
