{"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-55065 exists.","fix":"Upgrade code.vikunja.io/api to 2.4.0 or later.","what":"CVE-2026-55065 is a high-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-55065 and fix it if it is affected.\n\nWhat it is: CVE-2026-55065 is a high-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-55065 exists.\n\nAffected packages and fixed versions:\n- code.vikunja.io/api (Go): affected from 0.24.6; no fix listed\n- code.vikunja.io/api (Go): affected from 0.24.6; fixed in 2.4.0\n- code.vikunja.io/api (Go): affected from 0.24.6; 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-55065/ (Markdown: https://insights.sbomify.com/CVE-2026-55065/index.md)","id":"CVE-2026-55065","markdown":"https://insights.sbomify.com/CVE-2026-55065/index.md","name":"CVE-2026-55065","record":{"aliases":["GHSA-gg93-x632-9ccv","GO-2026-6313"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Vikunja task manager","requires_auth":"low_privilege","summary":"Authenticated users can delete Kanban assignments and ordering in other projects by supplying mismatched view identifiers, leading to unauthorized data modification.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"},{"id":"CWE-285","name":"Improper Authorization"}],"description":"Vikunja is an open-source self-hosted task management platform. From 0.24.6 until 2.4.0, DELETE /api/v1/projects/:project/views/:view permits an authenticated user to supply a view identifier from another project while authorizing only against an attacker-controlled project identifier. ProjectView.CanDelete in pkg/models/project_view_permissions.go does not establish that the view belongs to the path project, and ProjectView.Delete in pkg/models/project_view.go continues after the scoped project_views delete affects no rows. Its subsequent deletes select task_buckets and task_positions only by project_view_id, allowing cross-tenant destruction of Kanban assignments and ordering while leaving the victim view and tasks intact. 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: Improper Authorization and Authorization Bypass Through User-Controlled Key in code.vikunja.io/api","id":"CVE-2026-55065","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: Cross-tenant IDOR in kanban move-task endpoint via unauthorized body task_id","id":"CVE-2026-55066"},"packages":[{"ecosystem":"Go","fixed":[],"introduced":["0.24.6"],"last_affected":[],"package":"code.vikunja.io/api","purl":"pkg:golang/code.vikunja.io/api","source":"GO-2026-6313"},{"ecosystem":"Go","fixed":["2.4.0"],"introduced":["0.24.6"],"last_affected":[],"package":"code.vikunja.io/api","purl":null,"source":"GHSA-gg93-x632-9ccv"},{"ecosystem":"Go","fixed":["2.4.0"],"introduced":["0.24.6"],"last_affected":[],"package":"code.vikunja.io/api","purl":"pkg:golang/code.vikunja.io/api","source":"GHSA-gg93-x632-9ccv"}],"prev":{"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"},"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-09-01","vendors":["go-vikunja"]},"summary":"Authenticated users can delete Kanban assignments and ordering in other projects by supplying mismatched view identifiers, leading to unauthorized data modification.","url":"https://insights.sbomify.com/CVE-2026-55065/"}