Is CVE-2026-123528 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-123528 being exploited in the wild.

How severe is CVE-2026-123528?

Medium severity, with a CVSS score of 6.8, published 8 November 2026.

Is there a fix for CVE-2026-123528?

Yes: fixed in 2.7.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-123528 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-123528?

Check whether you run Vikunja at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-123528: Vikunja insufficient session expiration in HTTP token middleware

CVE-2026-123528 · Severity: medium · CVSS 6.8 · Published 2026-11-08

Vikunja is a task management and collaboration platform. After a user logs out, changes their password, or an administrator disables their account, stolen access tokens continue to work for up to 10 minutes and can be used to create longer-lived credentials that survive the revocation. This allows attackers to maintain persistent access to an account even after the user believes they have fully logged out.

Technologies: Vikunja. Vendors: Vikunja.

Quick answers

Is CVE-2026-123528 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-123528 being exploited in the wild.
How severe is CVE-2026-123528?: Medium severity, with a CVSS score of 6.8, published 8 November 2026.
Which products and versions are affected?: Vikunja before 2.7.1.
Is there a fix for CVE-2026-123528?: Yes: fixed in 2.7.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-123528 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-123528?: Check whether you run Vikunja at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 2.7.1

Technical details

The SetupTokenMiddleware validates JWT tokens only for signature and expiry but skips session and account-status checks, unlike the WebSocket authentication path which properly validates that the session still exists. An attacker with a valid access token can mint durable OAuth sessions (up to 72 hours) or API tokens with arbitrary expiry via /oauth/authorize and token creation endpoints, both of which survive logout and password reset. The vulnerability requires an already-valid token and cannot be exploited by unauthenticated users.

Affected products

Vikunja Vikunja before 2.7.1

Timeline

2026-10-22: disclosed
2026-11-08: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.