{"answers":{"affected":"3 open source packages ship an affected version, including code.vikunja.io/api.","exploited":"There is no known exploitation of GHSA-g38j-7v97-x298 in the wild and no public exploit code.","fix":"Upgrade code.vikunja.io/api to 2.6.0 or later.","what":"GHSA-g38j-7v97-x298 is a missing authorization vulnerability in code.vikunja.io/api, published on 9 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-g38j-7v97-x298 and fix it if it is affected.\n\nWhat it is: GHSA-g38j-7v97-x298 is a missing authorization vulnerability in code.vikunja.io/api, published on 9 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-g38j-7v97-x298 in the wild and no public exploit code.\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 all versions; fixed in 2.6.0\n- code.vikunja.io/api (Go): affected all versions; fixed in 2.6.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/GHSA-g38j-7v97-x298/ (Markdown: https://insights.sbomify.com/GHSA-g38j-7v97-x298/index.md)","id":"GHSA-g38j-7v97-x298","markdown":"https://insights.sbomify.com/GHSA-g38j-7v97-x298/index.md","name":"GHSA-g38j-7v97-x298","record":{"aliases":["GO-2026-6732"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_modify","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Vikunja task manager","requires_auth":"low_privilege","summary":"Authenticated users can bypass permission checks via CalDAV to create unauthorized task relations in projects they do not access.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Summary\nCreating a task relation over CalDAV does not run the `TaskRelation.CanCreate` permission check that the REST API enforces. An attacker can attach a relation to any task whose UID they know, including tasks in projects they have no access to. The identical operation over REST is correctly refused with 403.\n\n### Details\n`persistRelations` (`pkg/routes/caldav/listStorageProvider.go`, ~line 986) resolves the related task with an **unscoped** UID lookup (`models.GetTaskSimpleByUUID`) and calls `rel.Create(s, a)` directly, with no `CanCreate` check. `pkg/caldav/parsing.go` maps `RELATED-TO;RELTYPE=CHILD` to `RelationKindSubtask`. Because the CalDAV path never invokes the model's permission method, an authenticated user can create a subtask/parent relation between a task they own and an arbitrary victim task identified only by its UID.\n\nTask UIDs are `json:\"-\"` (never exposed over REST) but are exposed over CalDAV to anyone who has ever had read access to the containing project. Revoking that access does not unlearn the UID, so the realistic attacker is a removed collaborator.\n\nThis write primitive also feeds the cross-project subtask-disclosure issue (GHSA-3hc7-r24j-rpwc): it lets an attacker create the very cross-project subtask edge that read path leaks across, removing that finding's \"the attacker cannot create one to a project they can't access\" precondition.\n\nA secondary effect of the same unchecked path: the `createDummy` branch can `Create` a task unchecked when the referenced UID does not resolve.\n\n### PoC (verified at runtime against v2.5.0, commit c775a6c8)\nBaseline control — REST refuses:\n```\nPUT /api/v1/tasks/{attackerTask}/relations   (attacker JWT)\n{\"task_id\":{attackerTask},\"other_task_id\":{victimTask},\"relation_kind\":\"subtask\"}\n-\u003e HTTP 403 Forbidden\n```\nExploit — CalDAV succeeds:\n```\nPUT /dav/projects/{attackerProject}/{attackerTaskUID}.ics   (BasicAuth attacker)\nBEGIN:VCALENDAR\nVERSION:2.0\nBEGIN:VTODO\nUID:{attackerTaskUID}\nRELATED-TO;RELTYPE=CHILD:{victimTaskUID}\nEND:VTODO\nEND:VCALENDAR\n-\u003e HTTP 201\n```\nResult: a `task_relations` row is written with `task_id={victimTask}`, `relation_kind=parenttask`, `created_by_id={attacker}` — a persisted, attacker-attributable write onto a task in a project the attacker cannot access.\n\n### Impact\nBroken access control (missing authorization) on relation creation. An attacker can pollute the relation set of arbitrary tasks by UID and create the cross-project edges that enable subtask disclosure. Read of the related task's contents still requires the separate disclosure path; this finding is the unauthorized **write**.\n\n### Fix\nRoute CalDAV relation creation through `TaskRelation.CanCreate`, and scope the UID lookup to projects the caller can access.","ecosystems":["Go"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Creating a task relation over CalDAV does not run the `TaskRelation.CanCreate` permission check that the REST API enforces.","id":"GHSA-g38j-7v97-x298","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Go","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":3,"n_references":null,"packages":[{"ecosystem":"Go","fixed":[],"introduced":["0"],"last_affected":[],"package":"code.vikunja.io/api","purl":"pkg:golang/code.vikunja.io/api","source":"GO-2026-6732"},{"ecosystem":"Go","fixed":["2.6.0"],"introduced":["0"],"last_affected":[],"package":"code.vikunja.io/api","purl":null,"source":"GHSA-g38j-7v97-x298"},{"ecosystem":"Go","fixed":["2.6.0"],"introduced":["0"],"last_affected":[],"package":"code.vikunja.io/api","purl":"pkg:golang/code.vikunja.io/api","source":"GHSA-g38j-7v97-x298"}],"products":null,"published":"2026-10-09","related":[],"sources":[{"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"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Authenticated users can bypass permission checks via CalDAV to create unauthorized task relations in projects they do not access.","url":"https://insights.sbomify.com/GHSA-g38j-7v97-x298/"}