Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Vikunja versions before 2.3.0 have a two-factor authentication bypass in the OIDC login path. When OIDC email fallback matches a local user who has TOTP enabled, Vikunja issues a full login token without asking for the TOTP code. An attacker who can authenticate to the OIDC provider with a matching email address can gain access without the second factor. Upgrade to Vikunja 2.3.0 or later.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 7.4 | High | 3.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0029, the 22nd percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 15:05 UTC First seen by agentprime
- 31 Oct 2026, 15:05 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-8jvc-mcx6-r4cg
- OSV: GHSA-8jvc-mcx6-r4cg
- github.com/go-vikunja/vikunja/security/advisories/GHSA-8jvc-mcx6-r4cg
- nvd.nist.gov/vuln/detail/CVE-2026-34727
- github.com/go-vikunja/vikunja/pull/2582
- github.com/go-vikunja/vikunja/commit/b642b2a4536a3846e627a78dce2fdd1be425e6a1
- github.com/go-vikunja/vikunja
- github.com/go-vikunja/vikunja/releases/tag/v2.3.0