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.
Metrics
Affected Vendors & Products
References
History
Sun, 08 Nov 2026 05:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Go-vikunja
Go-vikunja vikunja |
|
| Vendors & Products |
Go-vikunja
Go-vikunja vikunja |
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: 2026-11-08T01:37:12.159Z
Updated: 2026-11-08T01:37:12.159Z
Reserved: 2026-11-06T00:44:37.659Z
Link: CVE-2026-123493
No data.
Status : Deferred
Published: 2026-11-08T02:16:36.183
Modified: 2026-11-08T02:16:36.350
Link: CVE-2026-123493
No data.