Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The Go module code.vikunja.io/api is affected in versions before 2.3.0, where the TOTP failed-attempt account lockout does not persist because the lock write is rolled back when the login handler rejects a TOTP code. An attacker who already has a user's password can brute-force 6-digit TOTP codes without the account being locked after 10 failures, though per-IP rate limiting slows attempts. Upgrade to version 2.3.0, which is listed as the fixed version.
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 |
|---|---|---|---|---|
| 5.9 | Medium | 3.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0031, the 23rd 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-fgfv-pv97-6cmj
- OSV: GHSA-fgfv-pv97-6cmj
- github.com/go-vikunja/vikunja/security/advisories/GHSA-fgfv-pv97-6cmj
- nvd.nist.gov/vuln/detail/CVE-2026-35597
- github.com/go-vikunja/vikunja/pull/2576
- github.com/go-vikunja/vikunja/commit/6ca0151d02fa0e8c7e2181ab916a28e08caaaec8
- github.com/go-vikunja/vikunja
- github.com/go-vikunja/vikunja/releases/tag/v2.3.0