Project Admin escalation via insufficient reparenting authorization
Published Apr 10, 2026 · Updated Apr 10, 2026
Improper privilege management in Vikunja before 2.3.0 allows remote authenticated users with inherited Write access to gain project Admin access. The CanUpdate check accepts Write permission on a new parent_project_id, while a recursive CTE then inherits the attacker-owned parent's Admin level on the moved project. Write access to a shared project is sufficient to delete it, alter sharing, or remove other users' access after reparenting.
Summary
What happened
Improper privilege management in Vikunja before 2.3.0 allows remote authenticated users with inherited Write access to gain project Admin access. The CanUpdate check accepts Write permission on a new parent_project_id, while a recursive CTE then inherits the attacker-owned parent's Admin level on the moved project. Write access to a shared project is sufficient to delete it, alter sharing, or remove other users' access after reparenting.
The record
- CVE
- CVE-2026-35595
- Published
- Apr 10, 2026
- Updated
- Apr 10, 2026
- Vendor
- Vikunja
- Product
- Vikunja
- Classifications
- CWE-269, T1068
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 10, 2026CVE publishedPublication date reported by the CVE source.
- Apr 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.3.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-2vq4-854f-5c72 project reparenting proof of conceptfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo