Vikunja: Link-share principal ID collision allows cross-account API token issuance and management — GHSA-VVCV-VPPH-H844
GitHub · GitHub · GHSA-VVCV-VPPH-H844
ID
GHSA-VVCV-VPPH-H844
GHSA-VVCV-VPPH-H844
Date
Source
GitHub
GitHub
Vendor
GitHub
GitHub
Threat
high
high
CVSS
8.1
8.1
EPSS
0.00464
0.00464
Summary
Executive Summary Vikunja accepts both regular-user JSON Web Tokens (JWTs) and link-share JWTs through its generic authenticated API route group. A link-share JWT resolves to a `models.LinkSharing` principal whose `GetID()` method returns the numeric `link_shares.id`. The API-token management model then treats that generic numeric value as a `users.id` when it creates, lists, and deletes API tokens. Because…
Timeline
- Published by source
- 2026-10-09
Risk context
- Reported severity or threat level: high.
- Reported CVSS score: 8.1 out of 10.
- Reported EPSS value: 0.00464.
- 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):
- Prioritize patching or mitigation immediately (treat as actively risky).
- 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
Evidence and provenance
- Canonical advisory ID
- GHSA-VVCV-VPPH-H844
- Source
- GitHub
- Vendor
- GitHub
- Published by source
- 2026-10-09
- Last source activity
- 2026-10-09
- Additional identifiers
- CVE-2026-68581
- Curated by
- hlukh.ch
Related advisories and connections
These advisories are connected by shared CVE, product, vendor, source, or time signals.