CVE-2026-68581: Vikunja 0.22.0 through 2.3.0 Authentication Bypass via Principal ID Collision

Published Aug 2, 2026
·
Updated

Vikunja versions 0.22.0 through 2.3.0 fail to validate the principal type in API token management. Because user IDs and link-share IDs are independent numeric sequences and both resolve through a generic web.Auth.GetID() interface, a link-share JWT whose numeric ID equals a target user's ID is treated as that user by the /api/v1/tokens endpoints. An authenticated attacker can obtain a target's numeric user ID via authenticated user search, then create link shares on an attacker-writable project until the link-share sequence reaches that value, and use the resulting link-share JWT to list, create, and delete the target user's API tokens (including issuing a new token with attacker-chosen scopes under the target's permissions). Fixed in version 2.4.0.

Affected Software

1 affected component
Vikunja>=0.22.0<=2.3.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Vikunja to a version that resolves this vulnerability.

    Fixed in 2.4.0
  2. Configuration

    Ensure API token management validates the principal type when handling authenticated principal identity (principal type validation was missing/failed in Vikunja versions 0.22.0 through 2.3.0).

    Vikunja API token management principal type validation = enabled

Event History

Aug 2, 2026
CVE Published
via MITRE·12:15 PM
Data Sourced
via MITRE·12:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·01:16 PM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-68581?

The severity of CVE-2026-68581 is rated as high with a score of 8.1.

2

How do I fix CVE-2026-68581?

To fix CVE-2026-68581, update Vikunja to version 2.3.1 or later which addresses the authentication bypass issue.

3

What vulnerability does CVE-2026-68581 describe?

CVE-2026-68581 describes an authentication bypass vulnerability in Vikunja due to Principal ID collision between user IDs and link-share IDs.

4

Which versions of Vikunja are affected by CVE-2026-68581?

Vikunja versions 0.22.0 through 2.3.0 are affected by CVE-2026-68581.

5

What are the potential impacts of CVE-2026-68581?

CVE-2026-68581 can lead to unauthorized access to user accounts due to incorrect validation of API token management.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203