Vikunja: Task relation deletion does not check read access to the other task, allowing cross-project relation removal — GHSA-W2CH-4XGR-22WW

Summary

## Summary Deleting a task relation only requires write access on the base task. Unlike relation creation, it does not verify that the caller can read the other task. A user with write access to one project can therefore delete relations whose other end lives in a project they have no access to. Since the delete removes both the forward and inverse rows, the relation also disappears for the other project's members.…

Timeline

Published by source

2026-10-09

Risk context

• Reported severity or threat level: low.
• Reported CVSS score: 2.3 out of 10.
• Review exposure for the affected product or family: go: code.vikunja.io/api.

Product

go: code.vikunja.io/api

What to do

General, cautious steps (verify details in the official source):

• Review exposure and plan remediation based on risk and environment.
• Identify affected product versions in your inventory and verify whether you are impacted.
• Apply vendor patches/updates or recommended mitigations as soon as available.
• Read the official advisory for exact affected versions and remediation steps.

Official advisory

• Read the official source

Evidence and provenance

Canonical advisory ID

GHSA-W2CH-4XGR-22WW

Source

GitHub

Vendor

GitHub

Published by source

2026-10-09

Last source activity

2026-10-09

Curated by

hlukh.ch

Related advisories and connections

These advisories are connected by shared CVE, product, vendor, source, or time signals.