Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

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

42
This month
CRITICAL 9.6UPGRADE

CVE-2026-33334 is a critical-severity flaw (CVSS 9.6) 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.21.0 and prior to version 2.2.0, the Vikunja Desktop Electron wrapper enables `nodeIntegration` in the renderer process without `contextIsolation` or `sandbox`. This means any cross-site scripting (XSS) vulnerability in the Vikunja web frontend -- present or future -- automatically escalates to full remote code execution on the victim's machine, as injected scri

Why this priority

  • Critical severity

A fixed release or distro patch exists.

Risk facts

CVSS score9.6 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionRequired
EPSS exploit chance0.4% (top 66%)
CISA exploited listNo
WeaknessCWE-94, CWE-269, CWE-79
Published2026-03-24
Last modified2026-06-17
Publisher (CNA): GitHub, Inc. · Vendor: vikunja

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

vikunja vikunja UPGRADE
Affected: >= 0.21.0 and < 2.2.2
Fixed in: 2.2.2
Safe to downgrade to: a release before 0.21.0
1. Check installed version
apt-cache policy vikunja || rpm -q vikunja || vikunja --version
2. UPGRADE to 2.2.2 (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.21.0 (Debian / Ubuntu)
apt-cache madison vikunja sudo apt install vikunja=<VERSION_BEFORE_0.21.0> 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.21.0> 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-33334?

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

Is CVE-2026-33334 being exploited?

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

CVE-2026-33334 affects vikunja. Severity is critical (CVSS 9.6). Vikunja is an open-source self-hosted task management platform. Starting in version 0.21.0 and prior to version 2.2.0, the Vikunja Desktop Electron wrapper enables `nodeIntegration` in the renderer process without `contextIsolation` or `san

How urgent is CVE-2026-33334?

Priority 42/100. Critical severity

Software pages

Electron vulnerabilities

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.