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

Routine

MEDIUM 5.7UPGRADE

CVE-2026-33473 is a medium-severity flaw (CVSS 5.7) 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. Starting in version 0.13 and prior to version 2.2.1, any user that has enabled 2FA can have their TOTP reused during the standard 30 second validity window. Version 2.2.1 patches the issue.

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	5.7 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	Required
EPSS exploit chance	0.3% (top 75%)
CISA exploited list	No
Weakness	CWE-287
Published	2026-03-24
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: vikunja

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

Am I affected?

Timeline

2026-03-24 16:16 UTCPublished CVE record published
2026-06-17 10:37 UTCUpdated Record last modified

vikunja vikunja UPGRADE

Affected: >= 0.13 and < 2.2.1

Fixed in: 2.2.1

Safe to downgrade to: a release before 0.13

1. Check installed version

apt-cache policy vikunja || rpm -q vikunja || vikunja --version

2. UPGRADE to 2.2.1 (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.

3. If no update is available yet, DOWNGRADE to a release before 0.13 (Debian / Ubuntu)

apt-cache madison vikunja sudo apt install vikunja=<VERSION_BEFORE_0.13> sudo apt-mark hold vikunja

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list vikunja sudo dnf downgrade vikunja-<VERSION_BEFORE_0.13> sudo dnf versionlock add vikunja

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

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-33473?

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

Is CVE-2026-33473 being exploited?

CVE-2026-33473 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-33473 affect?

CVE-2026-33473 affects vikunja. Severity is medium (CVSS 5.7). Vikunja is an open-source self-hosted task management platform. Starting in version 0.13 and prior to version 2.2.1, any user that has enabled 2FA can have their TOTP reused during the standard 30 second validity window. Version 2.2.1 patch

How urgent is CVE-2026-33473?

Priority 31/100. Public exploit reference

Related CVEs

CVE-2026-35597 MEDIUM 5.9 UPGRADE Vikunja is an open-source self-hosted task management platform
CVE-2026-35596 MEDIUM 4.3 UPGRADE Vikunja is an open-source self-hosted task management platform
CVE-2026-35594 MEDIUM 6.5 UPGRADE Vikunja is an open-source self-hosted task management platform
CVE-2026-35595 HIGH 8.3 UPGRADE Vikunja is an open-source self-hosted task management platform
CVE-2026-35599 MEDIUM 6.5 UPGRADE Vikunja is an open-source self-hosted task management platform

References

← Back to latest CVEs