Vikunja before 2.7.1 Insufficient Session Expiration via HTTP Token Middleware
Vikunja before 2.7.1 keeps accepting an already-issued access token after the account's sessions are revoked. Fixed in 2.7.1.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.7.1
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. The attacker must already hold a valid, previously issued access token (JWT) for the account. The user's sessions must have been revoked via logout, revoke sessions, password reset, or an administrator disabling the account. Affects Vikunja versions before 2.7.1 (confirmed on v2.7.0).
- Published
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 16/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.6/10CVSS 7.6
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
The attacker must already hold a valid, previously issued access token (JWT) for the account. The user's sessions must have been revoked via logout, revoke sessions, password reset, or an administrator disabling the account. Affects Vikunja versions before 2.7.1 (confirmed on v2.7.0).Upgrade to a fixed version: 2.7.1.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- go-vikunja vikunja
fixed in 2.7.1
Evidence 2
- Advisory
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-123528
Is CVE-2026-123528 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
Revoking a user's sessions through logout, revoking sessions, a password reset, or disabling the account does not stop an access token (JWT) issued earlier from working until it expires. That token keeps full authenticated HTTP access and can be used to create OAuth sessions or API tokens that outlast the revocation.Source: github.com, vulncheck.com
Which versions are affected by CVE-2026-123528?
vikunja: before 2.7.1.Source: cve.now feed data
Am I affected, and how do I check?
Vikunja versions before 2.7.1 are affected, and the advisory confirmed the issue on v2.7.0. To check a installation, compare the installed Vikunja version with 2.7.1. The issue applies only when a token was issued before the sessions were revoked.Source: github.com, vulncheck.com
How do I fix CVE-2026-123528?
Upgrade Vikunja to 2.7.1 or later, which is the listed fixed version.Source: github.com, vulncheck.com