CVSS 4.0
5.3 mediumCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:NCVE-2026-123493
Medium (5.3) in go-vikunja vikunja. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
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.
Severity
CVSS 3.1
5.4 mediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N- EPSS
- 0.2% estimated probability of exploitation activity in the next 30 days; 13th percentile. Scored 2026-11-10. A forecast for this CVE across the internet, not for your own systems.
- OWASP Top 10
- A07:2025 Authentication Failures
- Published
- Modified
- NVD analysis
- Deferred: the NVD does not plan to analyze it
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-123493 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-123493?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-123493?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-123493 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| go-vikunja vikunja | from 2.4.0 before 2.7.1 |