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

Q: How do I fix CVE-2026-34727?

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

Q: Is CVE-2026-34727 being exploited?

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

Q: What does CVE-2026-34727 affect?

CVE-2026-34727 affects vikunja. Severity is high (CVSS 7.4). Vikunja is an open-source self-hosted task management platform. Prior to 2.3.0, the OIDC callback handler issues a full JWT token without checking whether the matched user has TOTP two-factor authentication enabled. When a local user with T

Q: How urgent is CVE-2026-34727?

Priority 41/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

HIGH 7.4REMOTEUPGRADE

CVE-2026-34727 is a high-severity flaw (CVSS 7.4) 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 OIDC callback handler issues a full JWT token without checking whether the matched user has TOTP two-factor authentication enabled. When a local user with TOTP enrolled is matched via the OIDC email fallback mechanism, the second factor is completely skipped. This vulnerability is fixed in 2.3.0.

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.4 (High)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	0.3% (top 80%)
CISA exploited list	No
Weakness	CWE-287
Published	2026-04-10
Last modified	2026-10-26

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

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

Am I affected?

Timeline

2026-04-10 16:16 UTCPublished CVE record published
2026-10-26 00:10 UTCUpdated Record last modified

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

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

Is CVE-2026-34727 being exploited?

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

CVE-2026-34727 affects vikunja. Severity is high (CVSS 7.4). Vikunja is an open-source self-hosted task management platform. Prior to 2.3.0, the OIDC callback handler issues a full JWT token without checking whether the matched user has TOTP two-factor authentication enabled. When a local user with T

How urgent is CVE-2026-34727?

Priority 41/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

References

← Back to latest CVEs