Live › vulnerability › CVE-2026-57458
Go to dashboardVikunja, a self-hosted task manager, lets an API token scoped only to oauth.authorize exchange it for a full bearer JWT and refresh token. Those credentials are not limited by the token's scope, so an attacker with the scoped token can reach any route the same user can access.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:13 UTC, 0h before NVD. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| code.vikunja.io/api | go | all versions | – |
Check the deployed Vikunja version (2.3.0 is affected; the fix ships in 2.4.0), and list API tokens for any scoped to oauth.authorize.
2.4.0 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-57458")
Go Vulnerability Database, CC-BY 4.0 · EPSS scores by FIRST, used with attribution · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.