---
id: "CVE-2026-123493"
page: "https://infrastack.ai/live/CVE-2026-123493"
kind: "vulnerability"
aliases: ["CVE-2026-123493"]
title: "Vikunja: disabled users keep access through their bot users' API tokens"
severity: "medium"
cvss: 5.4
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["api-tokens", "package", "self-hosted", "vikunja"]
not_affected_if: ["no-bot-users", "version-2.7.1-or-later"]
published_at: "2026-11-08T02:16:36+00:00"
first_seen_at: "2026-11-08T02:21:07+00:00"
updated_at: "2026-11-08T02:25:16+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-123493", "first_seen_at": "2026-11-08T02:21:07+00:00"}]
exploit_sources: []
---

# Vikunja: disabled users keep access through their bot users' API tokens

Link for people: https://infrastack.ai/live/CVE-2026-123493 (this .md is for agents)

Vikunja, a self-hosted task manager, checks only the bot account's own status when validating API tokens. A disabled or locked user who already holds a token minted for a bot user can keep reading and changing shared projects over the API, CalDAV, MCP and feeds.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the Vikunja version with the server's version endpoint or the image tag; affected range is `2.4.0` up to but not including `2.7.1`.
- List bot users and their API tokens in the admin area and look for tokens still in use by accounts that were disabled or locked.

## Fix

- Vikunja: upgrade to `2.7.1` or later (per the NVD affected range).

## Timeline

- 2026-11-08T02:21:07+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-123493

## Documents

- [advisory] Vendor advisory: github.com https://github.com/go-vikunja/vikunja/security/advisories/GHSA-5fc2-w2j4-6r8w
- [advisory] Third-party advisory: www.vulncheck.com https://www.vulncheck.com/advisories/vikunja-from-2.4.0-before-2.7.1-authentication-bypass-via-bot-api-tokens

## From the sources

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.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_