Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 4.3amended

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

CVE-2026-55064GHSA-44v6-7fxq-vgf4

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (code.vikunja.io/api 2.4.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
4.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
EPSS
  • CVE-2026-55064: 0.37% estimated exploitation activity in the next 30 days; percentile 30.48 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary The fix for CVE-2026-35595 (project re-parenting privilege escalation) only gates reparent operations when parentprojectid 0. A user with Write (but not Admin) permission on a shared child project can detach it from its parent by sending parentprojectid: 0, bypassing the Admin requirement. This severs the recursive CTE permission inheritance chain, potentially disrupting the project hierarchy and affecting inherited access for other collaborators. Affected component - Package: go-vikunja/vikunja - Affected versions: v2.3.0 and later (including latest unstable v2.3.0-246-9852aff4). The fix for CVE-2026-35595 was introduced in v2.3.0 but left the detach-to-root case unpatched. Fixed in 2.4.0. - Tested on: Vikunja v2.3.0 (Docker image vikunja/vikunja:2.3.0) AND latest unstable (vikunja/vikunja:unstable, v2.3.0-246-9852aff4 built 2026-04-27) Technical detail Vulnerable code File: pkg/models/project.go (lines 1009-1041) File: pkg/models/projectpermissions.go (line 145) File:…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-44v6-7fxq-vgf4

  2. Revision 2 · amended ·

    Amended from osv record GO-2026-6306

  3. Revision 1 · created ·

    Published from osv record GHSA-44v6-7fxq-vgf4

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-55064

Advisory: Vikunja has an incomplete fix for CVE-2026-35595: Write-only user can detach shared project from parent hierarchy via parent_project_id=0
IDs: CVE-2026-55064, GHSA-44v6-7fxq-vgf4
Record: https://patchnext.com/advisories/cve-2026-55064 (revision 3, source checked 26 Oct 2026, 15:28 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: code.vikunja.io/api 2.4.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go code.vikunja.io/api: affected >= 2.3.0, < 2.4.0; fixed in 2.4.0

## Suggested inspection (read-only)
- Go code.vikunja.io/api: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on code.vikunja.io/api.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-44v6-7fxq-vgf4 (OSV record GHSA-44v6-7fxq-vgf4 lists affected ranges: Go code.vikunja.io/api >=2.3.0 <2.4.0 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6306 (OSV record GO-2026-6306 lists affected ranges: Go code.vikunja.io/api >=0)
- Verified: https://github.com/advisories/GHSA-44v6-7fxq-vgf4 (GitHub-reviewed advisory GHSA-44v6-7fxq-vgf4 lists affected ranges: Go code.vikunja.io/api >=2.3.0 <2.4.0)

Commands are suggestions: review each one before running it.

Loading voting…