Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-35597: Vikunja is an open-source self-hosted task management platform

36
This week
MEDIUM 5.9REMOTEUPGRADE

CVE-2026-35597 is a medium-severity flaw (CVSS 5.9) affecting vikunja. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Vikunja is an open-source self-hosted task management platform. Prior to 2.3.0, the TOTP failed-attempt lockout mechanism is non-functional due to a database transaction handling bug. When a TOTP validation fails, the login handler in pkg/routes/api/v1/login.go calls HandleFailedTOTPAuth and then unconditionally rolls back. HandleFailedTOTPAuth in pkg/user/totp.go uses an in-memory counter (key-value store) to track failed attempts. When the coun

Why this priority

  • Public exploit reference
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score5.9 (Medium)
Attack vectorNetwork (remote)
Attack complexityHigh
Privileges neededNone
User interactionNone
EPSS exploit chance0.3% (top 78%)
CISA exploited listNo
WeaknessCWE-307
Published2026-04-10
Last modified2026-10-26
Publisher (CNA): GitHub, Inc. · Vendor: vikunja

Share: LinkedIn · X · Reddit

Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

vikunja vikunja UPGRADE
Affected: < 2.3.0
Fixed in: 2.3.0
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy vikunja || rpm -q vikunja || vikunja --version
2. UPGRADE to 2.3.0 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade vikunja
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade vikunja
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-35597?

vikunja: upgrade to 2.3.0. Exact commands for each OS are on this page.

Is CVE-2026-35597 being exploited?

CVE-2026-35597 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-35597 affect?

CVE-2026-35597 affects vikunja. Severity is medium (CVSS 5.9). Vikunja is an open-source self-hosted task management platform. Prior to 2.3.0, the TOTP failed-attempt lockout mechanism is non-functional due to a database transaction handling bug. When a TOTP validation fails, the login handler in pkg/r

How urgent is CVE-2026-35597?

Priority 36/100. Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.