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 scripts gain access to Node.js APIs. Version 2.2.0 fixes the issue.
CVE-2026-33334
This critical-severity CVE scores 9.6 under NVD CVSS v3. EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.6
- EG Score
- 9.6(low)
- EG Risk
- 48(Track)EG Risk 48/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity96% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 31%
- KEV
- Not listed
Published
March 24, 2026
Last Modified
June 17, 2026
Advisory Details (2)
Auto-updated Jul 27, 2026Vikunja 2.2.0: Ten security fixes, Gantt overhaul, and task duplication
https://vikunja.io/changelog/vikunja-v2.2.0-was-releasedAny frontend XSS escalates to Remote Code Execution due to nodeIntegration in Vikunja Desktop · Advisory · go-vikunja/vikunja · GitHub
https://github.com/go-vikunja/vikunja/security/advisories/GHSA-xh67-63q3-hf7gWeakness Classification(3)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-27 14:30 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-94 · CWE-269
- CVE-2003-1432EG 10.0EPSS p94HIGH
- CVE-2002-0495EG 10.0EPSS p96HIGH
- CVE-1999-0702EG 10.0EPSS p98HIGH
- CVE-1999-0509EG 10.0EPSS p98HIGH
- CVE-2002-0367NVD 7.8EG 9.0 KEVEPSS p91CRITICAL
- CVE-1999-0084EG 8.4HIGH
- CVE-2003-1227EG 7.5EPSS p93HIGH
- CVE-2003-1240EG 7.5EPSS p93HIGH
- CVE-2003-1253EG 7.5HIGH
- CVE-2003-1406EG 7.5HIGH
Frequently asked(5)
What is CVE-2026-33334?
When was CVE-2026-33334 disclosed?
Is CVE-2026-33334 actively exploited?
What is the CVSS score of CVE-2026-33334?
How do I remediate CVE-2026-33334?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-33334
Is Your Infrastructure Affected by CVE-2026-33334?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.