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

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

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

Q: Is CVE-2026-33313 being exploited?

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

CVE-2026-33313 affects vikunja. Severity is medium (CVSS 4.3). Vikunja is an open-source self-hosted task management platform. Prior to version 2.2.0, an authenticated user can read any task comment by ID, regardless of whether they have access to the task the comment belongs to, by substituting the ta

Q: How urgent is CVE-2026-33313?

Priority 20/100. No elevated risk signals yet.

Routine

MEDIUM 4.3UPGRADE

CVE-2026-33313 is a medium-severity flaw (CVSS 4.3) 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 version 2.2.0, an authenticated user can read any task comment by ID, regardless of whether they have access to the task the comment belongs to, by substituting the task ID in the API URL with a task they do have access to. Version 2.2.0 fixes the issue.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	4.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.3% (top 80%)
CISA exploited list	No
Weakness	CWE-639
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 15:16 UTCPublished CVE record published
2026-06-17 10:37 UTCUpdated Record last modified

vikunja vikunja UPGRADE

Affected: < 2.2.0

Fixed in: 2.2.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.2.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-33313?

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

Is CVE-2026-33313 being exploited?

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

CVE-2026-33313 affects vikunja. Severity is medium (CVSS 4.3). Vikunja is an open-source self-hosted task management platform. Prior to version 2.2.0, an authenticated user can read any task comment by ID, regardless of whether they have access to the task the comment belongs to, by substituting the ta

How urgent is CVE-2026-33313?

Priority 20/100. No elevated risk signals yet.

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