CVE-2026-123528
Vikunja before 2.7.1 contains an insufficient session expiration vulnerability that allows holders of revoked access tokens to keep authenticating because Setu…
Impact
Vikunja before 2.7.1 contains an insufficient session expiration vulnerability that allows holders of revoked access tokens to keep authenticating because SetupTokenMiddleware skips session and account-status checks. Attackers with a stolen token can, after logout, password reset, or account disabling, mint OAuth sessions via /oauth/authorize or tk_ API tokens for persistent access.
An attacker can exploit this over the network, with a regular user account, without any action by a user. Specific conditions have to be met, which makes an attack harder. If it succeeds: high risk of data being read, high risk of data or systems being changed.
Affected products · Go-vikunja
| Product | Affected versions |
|---|---|
| Vikunja | before 2.7.1 |
Weakness classification
References
- NVD record
- CVE.org record
- GitHub advisory
- https://github.com/go-vikunja/vikunja/security/advisories/GHSA-4qvp-948j-4cgv
- https://www.vulncheck.com/advisories/vikunja-before-2.7.1-insufficient-session-expiration-via-http-token-middleware
- https://github.com/advisories/GHSA-vvrr-xxjj-fc78
- https://nvd.nist.gov/vuln/detail/CVE-2026-123528