Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Vikunja versions 2.3.0 up to but not including 2.4.0 are affected. A scoped API token limited only to the oauth.authorize permission can use the OAuth authorization flow to obtain a normal JWT and refresh token for the same user, and those credentials are not restricted by the token's scope. An attacker who holds such a token can then reach routes outside its declared permissions, such as the user and project endpoints. Upgrade to Vikunja 2.4.0 or later, which is the listed fixed version.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 8.1 | High | 3.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0033, the 26th percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:11 UTC First seen by agentprime
- 31 Oct 2026, 14:11 UTC Confirmed by OSV