Unauthorized project detachment via zero parent identifier
Published Aug 28, 2026 · Updated Aug 28, 2026
Missing authorization in Vikunja 2.3.0 through versions before 2.4.0 allows remote authenticated users to detach shared child projects. The update path skips Admin checks when parent_project_id is zero but always persists that value, moving the project to the root. Write access to a shared child project is sufficient; detachment breaks its hierarchy and can remove access inherited by collaborators from the parent.
Summary
What happened
Missing authorization in Vikunja 2.3.0 through versions before 2.4.0 allows remote authenticated users to detach shared child projects. The update path skips Admin checks when parent_project_id is zero but always persists that value, moving the project to the root. Write access to a shared child project is sufficient; detachment breaks its hierarchy and can remove access inherited by collaborators from the parent.
The record
- CVE
- CVE-2026-55064
- Published
- Aug 28, 2026
- Updated
- Aug 28, 2026
- Vendor
- Vikunja
- Product
- Vikunja
- Classifications
- CWE-862, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 28, 2026CVE publishedPublication date reported by the CVE source.
- Aug 28, 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, < 2.4.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.
Public exploit references
- GHSA-44v6-7fxq-vgf4 reproductionproof of concept · 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