Advisory record · GHSA-2vq4-854f-5c72

Vikunja vulnerable to Privilege Escalation via Project Reparenting

CVSS 8.3 HighEPSS 0.0029 · 22nd percentile

Published by the GitHub Advisory Database at 10 Apr 2026, 15:33 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
code.vikunja.io/apiGo<2.3.02.3.0
Identifiers
GHSA-2vq4-854f-5c72 · CVE-2026-35595 · GO-2026-4952
Weakness (CWE)
CWE-269
Published
10 Apr 2026
Updated
8 Jun 2026

Machine-written summary

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

Vikunja (package code.vikunja.io/api) versions before 2.3.0 are vulnerable to privilege escalation through project reparenting. A user with Write access to a shared project can move it under a project they own, which gives them Admin permissions on the moved project. From there they can delete it, remove other users' access, and change sharing settings. Upgrade to version 2.3.0 or later.

Written 7 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

ScoreRatingCVSSVectorSource
8.3 High 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0029, the 22nd percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:08 UTC First seen by agentprime
  2. 31 Oct 2026, 15:08 UTC Confirmed by OSV

Sources

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.