{"answers":{"affected":"3 open source packages ship an affected version, including code.vikunja.io/api.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55064 exists.","fix":"Upgrade code.vikunja.io/api to 2.4.0 or later.","what":"CVE-2026-55064 is a medium-severity missing authorization vulnerability in go-vikunja vikunja, published on 28 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-55064 and fix it if it is affected.\n\nWhat it is: CVE-2026-55064 is a medium-severity missing authorization vulnerability in go-vikunja vikunja, published on 28 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55064 exists.\n\nAffected packages and fixed versions:\n- code.vikunja.io/api (Go): affected all versions; no fix listed\n- code.vikunja.io/api (Go): affected from 2.3.0; fixed in 2.4.0\n- code.vikunja.io/api (Go): affected from 2.3.0; fixed in 2.4.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-55064/ (Markdown: https://insights.sbomify.com/CVE-2026-55064/index.md)","id":"CVE-2026-55064","markdown":"https://insights.sbomify.com/CVE-2026-55064/index.md","name":"CVE-2026-55064","record":{"aliases":["GHSA-44v6-7fxq-vgf4","GO-2026-6306"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["privilege_escalation","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Vikunja task manager","requires_auth":"low_privilege","summary":"A write-only user can detach a shared project from its parent hierarchy, bypassing admin checks and disrupting permission inheritance.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"Vikunja is an open-source self-hosted task management platform. From 2.3.0 until 2.4.0, a user with Write but not Admin permission on a shared child project can detach it from its parent hierarchy by submitting parent_project_id equal to 0 to POST /api/v1/projects/{project}. The Project.CanUpdate authorization check in pkg/models/project_permissions.go and UpdateProject logic in pkg/models/project.go only gate nonzero parent values, while UpdateProject always persists parent_project_id, so the explicit zero value bypasses the Admin requirement introduced for CVE-2026-35595. Detachment severs the recursive permission-inheritance chain and can disrupt the owner’s hierarchy and inherited collaborator access. This issue is fixed in version 2.4.0.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Vikunja has an incomplete fix for CVE-2026-35595: Write-only user can detach shared project from parent hierarchy via parent_project_id=0","id":"CVE-2026-55064","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"Vikunja: Improper Authorization and Authorization Bypass Through User-Controlled Key in code.vikunja.io/api","id":"CVE-2026-55065"},"packages":[{"ecosystem":"Go","fixed":[],"introduced":["0"],"last_affected":[],"package":"code.vikunja.io/api","purl":"pkg:golang/code.vikunja.io/api","source":"GO-2026-6306"},{"ecosystem":"Go","fixed":["2.4.0"],"introduced":["2.3.0"],"last_affected":[],"package":"code.vikunja.io/api","purl":null,"source":"GHSA-44v6-7fxq-vgf4"},{"ecosystem":"Go","fixed":["2.4.0"],"introduced":["2.3.0"],"last_affected":[],"package":"code.vikunja.io/api","purl":"pkg:golang/code.vikunja.io/api","source":"GHSA-44v6-7fxq-vgf4"}],"prev":{"headline":"uniget: Path Traversal in Hook Files - Directory Escape Vulnerability","id":"CVE-2026-55062"},"products":["vikunja"],"published":"2026-08-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-28","vendors":["go-vikunja"]},"summary":"A write-only user can detach a shared project from its parent hierarchy, bypassing admin checks and disrupting permission inheritance.","url":"https://insights.sbomify.com/CVE-2026-55064/"}