Vikunja: Webhooks and link shares survive every revocation path, so a removed collaborator keeps a live feed
CVE-2026-111919GHSA-hjx8-qv73-f7cm
What to do
Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Go code.vikunja.io/api
- Affected
- >= 0.22.0, <= 2.6.0
- Fixed in
- no fixed version recorded
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GO-2026-6733 lists affected ranges: Go code.vikunja.io/api >=0.22.0
VerifiedObserved Structured OSV record; not marked as GitHub-reviewed.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-hjx8-qv73-f7cm lists affected ranges: Go code.vikunja.io/api >=0.22.0 <=2.6.0
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-hjx8-qv73-f7cm lists affected ranges: Go code.vikunja.io/api >=0.22.0 <=2.6.0
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 6.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- EPSS
- CVE-2026-111919: 0.36% estimated exploitation activity in the next 30 days; percentile 29.30 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
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 {taskassignees, subscriptions}. webhooks and linkshares — the only two rows that carry a live channel into the project — are not in it, and the routine is wired to one of four revocation paths. Details pkg/models/teams.go:411 — cleanupTaskMembersAfterTeamRemoval, added in 9358954c9, whose commit message states the invariant: "cleanup team memberships, assignments and subscriptions when users lose access to a project". So you have already decided that losing read access must delete rows the departing user left behind, and that the test is a live project.CanRead. The gap is which rows are in the set. And there is a second level, which is the sharper one. That routine has…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-hjx8-qv73-f7cm
- Revision 2 · amended ·
Amended from osv record GO-2026-6733
- Revision 1 · created ·
Published from osv record GHSA-hjx8-qv73-f7cm
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-111919 Advisory: Vikunja: Webhooks and link shares survive every revocation path, so a removed collaborator keeps a live feed IDs: CVE-2026-111919, GHSA-hjx8-qv73-f7cm Record: https://patchnext.com/advisories/cve-2026-111919 (revision 3, source checked 26 Oct 2026, 15:32 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 6.5) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed. ## Affected components - Go code.vikunja.io/api: affected >= 0.22.0, <= 2.6.0 ## Suggested inspection (read-only) - Go code.vikunja.io/api: check the installed version with your package manager. ## Supported action No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on code.vikunja.io/api. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GO-2026-6733 (OSV record GO-2026-6733 lists affected ranges: Go code.vikunja.io/api >=0.22.0) - Verified: https://osv.dev/vulnerability/GHSA-hjx8-qv73-f7cm (OSV record GHSA-hjx8-qv73-f7cm lists affected ranges: Go code.vikunja.io/api >=0.22.0 <=2.6.0) - Verified: https://github.com/advisories/GHSA-hjx8-qv73-f7cm (GitHub-reviewed advisory GHSA-hjx8-qv73-f7cm lists affected ranges: Go code.vikunja.io/api >=0.22.0 <=2.6.0) Commands are suggestions: review each one before running it.
Loading voting…