Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Sun, 08 Nov 2026 01:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Vikunja from 2.4.0 before 2.7.1 contains an authentication bypass vulnerability that allows disabled or locked users to retain access through API tokens owned by their bot users. Because token validation only checks the bot's own status, attackers holding pre-minted bot tokens can keep reading and modifying shared projects via the HTTP API, CalDAV, MCP and feeds. | |
| Title | Vikunja from 2.4.0 before 2.7.1 Authentication Bypass via Bot API Tokens | |
| First Time appeared |
Vikunja
Vikunja vikunja |
|
| Weaknesses | CWE-613 | |
| CPEs | cpe:2.3:a:vikunja:vikunja:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Vikunja
Vikunja vikunja |
|
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: VulnCheck
Published:
Updated: 2026-11-08T01:37:12.159Z
Reserved: 2026-11-06T00:44:37.659Z
Link: CVE-2026-123493
No data.
No data.
No data.
OpenCVE Enrichment
No data.
-
CWE-613
Insufficient Session Expiration