CVE-2026-57458 Vikunja: Scoped API token can mint unrestricted OAuth session credentials
Attackers with scoped API tokens can mint unrestricted OAuth credentials, bypassing permission limits to access unauthorized data in Vikunja.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-57458?
CVE-2026-57458 is a high-severity vulnerability in go-vikunja vikunja, published on 9 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Vikunja is an open-source self-hosted task management platform. In version 2.3.0, a scoped API token limited to the `oauth.authorize` permission can call `POST /api/v1/oauth/authorize`, obtain an OAuth authorization code, and exchange the code at `POST /api/v1/oauth/token` for a normal bearer JSON Web Token (JWT) and refresh token. The resulting credentials are not restricted by the original API token's permissions, allowing access to routes outside its declared scope for the same user. Version 2.4.0 fixes the vulnerability.
Weakness: CWE-269
Which versions are affected by CVE-2026-57458?
3 open source packages ship an affected version, including code.vikunja.io/api.
| Package | Affected | Fixed in |
|---|---|---|
code.vikunja.io/api Go | All versions | None |
code.vikunja.io/api Go | From 2.3.0 | 2.4.0 |
code.vikunja.io/api Go | From 2.3.0 | 2.4.0 |
How do I fix CVE-2026-57458?
Upgrade code.vikunja.io/api to 2.4.0 or later.
Is CVE-2026-57458 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-57458 exists.
Sources
Also known as GHSA-v3p6-34mc-hj7v, GO-2026-6750.