Vikunja: Scoped API token can mint unrestricted OAuth session credentials — GHSA-V3P6-34MC-HJ7V
GitHub · GitHub · GHSA-V3P6-34MC-HJ7V
ID
GHSA-V3P6-34MC-HJ7V
GHSA-V3P6-34MC-HJ7V
Date
Source
GitHub
GitHub
Vendor
GitHub
GitHub
Threat
high
high
CVSS
8.1
8.1
Summary
## Summary A scoped API token can bypass its declared permissions by using the OAuth authorization flow to mint normal session credentials. A token limited to: ```json {"oauth":["authorize"]} ``` can call `/api/v1/oauth/authorize`, receive an OAuth authorization code, exchange it at `/api/v1/oauth/token`, and obtain a normal bearer JWT plus refresh token. The resulting credentials are not restricted by the original…
Timeline
- Published by source
- 2026-10-09
Risk context
- Reported severity or threat level: high.
- Reported CVSS score: 8.1 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):
- 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-V3P6-34MC-HJ7V
- Source
- GitHub
- Vendor
- GitHub
- Published by source
- 2026-10-09
- Last source activity
- 2026-10-09
- Additional identifiers
- CVE-2026-57458
- Curated by
- hlukh.ch
Related advisories and connections
These advisories are connected by shared CVE, product, vendor, source, or time signals.