GHSA-g38j-7v97-x298: Vikunja: CalDAV relation creation bypasses TaskRelation.CanCreate, allowing an unauthorized write into any task by known UID
Summary Creating 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.
Published Oct 9, 2026
Affected packages
code.vikunja.io/api
- Ecosystem
- Go
- Affected
- <= 2.5.0
- Fixed in
- 2.6.0
- Check
go list -m code.vikunja.io/api
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
Creating 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.
Details
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.
Task 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.
This 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.
A secondary effect of the same unchecked path: the createDummy branch can Create a task unchecked when the referenced UID does not resolve.
PoC (verified at runtime against v2.5.0, commit c775a6c8)
Baseline control — REST refuses:
PUT /api/v1/tasks/{attackerTask}/relations (attacker JWT)
{"task_id":{attackerTask},"other_task_id":{victimTask},"relation_kind":"subtask"}
-> HTTP 403 ForbiddenExploit — CalDAV succeeds:
PUT /dav/projects/{attackerProject}/{attackerTaskUID}.ics (BasicAuth attacker)
BEGIN:VCALENDAR
VERSION:2.0
BEGIN:VTODO
UID:{attackerTaskUID}
RELATED-TO;RELTYPE=CHILD:{victimTaskUID}
END:VTODO
END:VCALENDAR
-> HTTP 201Result: 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.
Impact
Broken 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.
Fix
Route CalDAV relation creation through TaskRelation.CanCreate, and scope the UID lookup to projects the caller can access.
Credited to JellowBeanz26.
References
- https://github.com/go-vikunja/vikunja/security/advisories/GHSA-g38j-7v97-x298
- https://github.com/go-vikunja/vikunja/pull/3688
- https://github.com/go-vikunja/vikunja/commit/077dc4de79ce6f1ab59215a2c7bf9b30423685f2
- https://github.com/go-vikunja/vikunja/releases/tag/v2.6.0
- https://github.com/advisories/GHSA-g38j-7v97-x298
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-57458
Vikunja: Scoped API token can mint unrestricted OAuth session credentials
high8.1Oct 9, 2026CVE-2026-62367
Vikunja: OIDC email-fallback account linking ignores email_verified, enabling local-account takeover
high7.5Oct 9, 2026CVE-2026-62376
Vikunja: Plaintext storage of password-reset/email-confirm tokens in database enables account takeover on DB read access
high8.1Oct 9, 2026CVE-2026-68581
Vikunja: Link-share principal ID collision allows cross-account API token issuance and management
high8.1Oct 9, 2026CVE-2026-68582
Vikunja: Link-share token reads any tenant's kanban buckets and enumerates usernames/IDs instance-wide (BOLA)
critical9.3Oct 9, 2026CVE-2026-76216
Vikunja: Link-share principal-type confusion enables cross-account team removal, bot takeover, and roster disclosure
high7.5Oct 9, 2026
