Skip to main content
CVE-2026-123493VulnerabilityPublished

Vikunja from 2.4.0 before 2.7.1 contains an authentication bypass vulnerability that allows disabled or locked users

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-123493· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium : upgrade to 2.7.1 when convenient.

Data as of 8 Nov 2026, 07:02 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.05.3
CNA (VulnCheck)CVSS 3.15.4
Patch
Available – fixed in 2.7.1
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 7 Nov 2026.

What to do

Upgrade vikunja to 2.7.1.

Affected software

ProductAffectedFixed in
go-vikunjavikunjaAffected
  • >=2.4.0 <2.7.1
Fixed in
  • 2.7.1
Govikunjapkg:golang/vikunjaOther threatsAffected
  • >=2.4.0 <2.7.1
Fixed in
  • 2.7.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in Vikunja version 2.7.1, which addresses this authentication bypass vulnerability. Users should upgrade to version 2.7.1 or later to remediate this issue. Until patched, restrict use of bot tokens associated with disabled or locked users where possible.

Description

Vikunja versions from 2.4.0 up to but not including 2.7.1 have an authentication bypass vulnerability. This flaw allows disabled or locked users to maintain access via API tokens associated with their bot users. The vulnerability arises because token validation only verifies the bot user's status, not the status of the original user. Attackers with pre-existing bot tokens can continue to read and modify shared projects through multiple interfaces including the HTTP API, CalDAV, MCP, and feeds.

References

Community reviews

Loading reviews…