CVE-2026-123493

Vikunja from 2.4.0 before 2.7.1 Authentication Bypass via Bot API Tokens

  • Medium 5.4

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.

Key facts

Published
8 Nov 2026
Last changed
10 Nov 2026
Assigned by
VulnCheck
EPSS
0.226% likely to be exploited in the next 30 days, higher than 13.457% of CVEs (scores for 15 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 5.3CVSS 4.0, Mediumfrom the CNA (VulnCheck)CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
  • 5.4CVSS 3.1, Mediumfrom the CNA (VulnCheck)CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
go-vikunjavikunja
  • Default status: unaffected
  • 2.4.0 up to but excluding 2.7.1 (affected)
  • 2.7.1 (unaffected)

Timeline

  1. 8 Nov 2026 Published

Weakness

References