Vikunja: Webhooks and link shares survive every revocation path, so a removed collaborator keeps a live feed — GHSA-HJX8-QV73-F7CM

Summary

## Summary A collaborator removed from a project keeps a **live, automatic feed** of that project's contents, because nothing on any revocation path deletes the webhook they created while they had access. Vikunja already has a revocation-cleanup routine that deletes other derived rows for exactly this reason. Its set is `{task_assignees, subscriptions}`. **`webhooks` and `link_shares` — the only two rows that carry…

Timeline

Published by source

2026-10-09

Risk context

• Reported severity or threat level: medium.
• Reported CVSS score: 6.5 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-HJX8-QV73-F7CM

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.