{"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-54766 exists.","fix":"Upgrade code.vikunja.io/api to 2.4.0 or later.","what":"CVE-2026-54766 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-54766 and fix it if it is affected.\n\nWhat it is: CVE-2026-54766 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-54766 exists.\n\nAffected packages and fixed versions:\n- code.vikunja.io/api (Go): affected from 0.21.0; no fix listed\n- code.vikunja.io/api (Go): affected from 0.21.0; fixed in 2.4.0\n- code.vikunja.io/api (Go): affected from 0.21.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-54766/ (Markdown: https://insights.sbomify.com/CVE-2026-54766/index.md)","id":"CVE-2026-54766","markdown":"https://insights.sbomify.com/CVE-2026-54766/index.md","name":"CVE-2026-54766","record":{"aliases":["GHSA-f27p-pw2p-9pr4","GO-2026-6311"],"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 bypass write-permission checks to inject content into arbitrary project hierarchies during project duplication.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"},{"id":"CWE-285","name":"Improper Authorization"}],"description":"Vikunja is an open-source self-hosted task management platform. From 0.21.0 until 2.4.0, the project duplication operation in pkg/models/project_duplicate.go allows an authenticated user who can read a source project to place its duplicate beneath an arbitrary target parent project. ProjectDuplicate.CanCreate calls parent.CanCreate on an unhydrated Project containing only the body supplied parent_project_id instead of calling parent.CanWrite, so the target parent write-permission check is skipped. The ordinary project creation path enforces that permission, but PUT /api/v1/projects/{project}/duplicate does not, allowing attacker-owned content to be injected into another user or team project hierarchy. 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: Project duplication bypasses write-permission check on the target parent project","id":"CVE-2026-54766","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":"WeGIA: Hardcoded Secret Key Backdoor — Mass Data Destruction via deletar_socios.php","id":"CVE-2026-54767"},"packages":[{"ecosystem":"Go","fixed":[],"introduced":["0.21.0"],"last_affected":[],"package":"code.vikunja.io/api","purl":"pkg:golang/code.vikunja.io/api","source":"GO-2026-6311"},{"ecosystem":"Go","fixed":["2.4.0"],"introduced":["0.21.0"],"last_affected":[],"package":"code.vikunja.io/api","purl":null,"source":"GHSA-f27p-pw2p-9pr4"},{"ecosystem":"Go","fixed":["2.4.0"],"introduced":["0.21.0"],"last_affected":[],"package":"code.vikunja.io/api","purl":"pkg:golang/code.vikunja.io/api","source":"GHSA-f27p-pw2p-9pr4"}],"prev":{"headline":"Traefik: Gateway HTTPRoute backendRef filters can leak backend context across routes sharing a Service:port","id":"CVE-2026-54765"},"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":"Authenticated users can bypass write-permission checks to inject content into arbitrary project hierarchies during project duplication.","url":"https://insights.sbomify.com/CVE-2026-54766/"}