Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2021 - Vulnerable and Outdated Components
ASVS 5.0
V4 - API and Web Service Improper authorization in handler
|
| Impact | While a formal CVSS score and EPSS probability are not provided, the risk is substantial based on available signals. The attack vector is network-based and requires no privileges (attacker only needs to inject a link into content the victim views), making it trivially exploitable. The complexity is low—any user-generated content field (comments, task descriptions, notes) can carry the malicious payload. The technical impact is severe: arbitrary code execution or file access is possible depending on the OS and installed applications. The vulnerability affects the Desktop application, which is typically run by end-users on workstations where local file access and application invocation pose significant risk (information disclosure, privilege escalation, lateral movement). The GitHub advisory and changelog reference indicate vendor awareness and a released patch (v2.2.0), reducing urgency for vendors but creating a window of exposure for unpatched deployments. The lack of a public POC does not diminish exploitability—the attack surface is enormous (any website or plugin that injects HTML with target="_blank" links). This is a high-priority vulnerability for all desktop users; the real-world impact depends on what trusted applications and files are accessible on each victim's system. |
| Exploit ScenarioDerived | A malicious user embeds a link such as <a href="file:///etc/passwd" target="_blank">Click for details</a> or <a href="ms-settings:appsfeatures" target="_blank">Update</a> in a Vikunja task description or comment. When a victim using Vikunja Desktop (v0.21.0–v2.1.x) clicks the link or the page auto-triggers window.open(), the Electron wrapper passes the URI directly to the OS without validation, causing the victim's file manager to open a sensitive file or a system settings panel to launch. On Linux, an attacker could craft a link like apt:package-name to trigger package installation or xdg-open with a local path to exfiltrate file contents. The attack requires only network-level injection of HTML and exploits the implicit trust users place in content displayed within the application, making it practical and difficult to detect without analyzing page sources. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 24, 2026
The Vikunja Desktop Electron application fails to validate or allowlist URI schemes before passing URLs from window.open() calls to shell.openExternal(), allowing attackers to invoke arbitrary local applications, open files, or trigger custom protocol handlers. Vikunja versions 0.21.0 through 2.1.x are affected, with the vulnerability patched in version 2.2.0. An attacker who can inject links with target="_blank" into user-generated content can exploit this to execute malicious actions on the victim's operating system without user awareness or explicit consent.
RemediationAI
Immediately upgrade the Vikunja Desktop application to version 2.2.0 or later; this is the primary and complete remediation. Users unable to upgrade immediately should disable or restrict Electron's preload/context isolation settings if possible (consult Vikunja documentation), or avoid opening untrusted content (tasks, comments, descriptions) from external sources until patching is complete. Administrators distributing Vikunja Desktop should prioritize deployment of v2.2.0 via their software distribution mechanism. For organizations using the self-hosted web version, no action is required; the vulnerability is confined to the Electron wrapper. Monitor the GitHub advisory at https://github.com/go-vikunja/vikunja/security/advisories/GHSA-6q44-85gc-cjvf for any post-patch updates or additional guidance.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability exists in the Vikunja Desktop Electron wrapper (CPE: cpe:2.3:a:go-vikunja:vikunja). Electron's shell.openExternal() API is designed to open URLs and URI schemes using the operating system's default handlers. The root cause is classified under CWE-939 (Improper Authorization in Other Contexts), more specifically a failure to implement protocol allowlisting or URI validation before invoking system-level URI handlers. When a web page running within Electron calls window.open() with an attacker-controlled URL, the wrapper directly passes this to shell.openExternal() without sanitization, causing the OS to honor dangerous URI schemes such as file://, custom protocol handlers, or application-launching schemes (e.g., ms-settings:, apt:, etc.). This is a classic instance of inadequate trust boundary enforcement between the web context and the native OS layer.
Know when Vikunja gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H
Primary rating from GitHub Advisory · only source for this CVE.
CVSS VectorGitHub Advisory
Lifecycle Timeline
2DescriptionGitHub Advisory
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 passes URLs from window.open() calls directly to shell.openExternal() without any validation or protocol allowlisting. An attacker who can place a link with target="_blank" (or that otherwise triggers window.open) in user-generated content can cause the victim's operating system to open arbitrary URI schemes, invoking local applications, opening local files, or triggering custom protocol handlers. Version 2.2.0 patches the issue.
Executive ViewAI
Organizations using version 0.21.0 and should be aware of moderate risk from CVE-2026-33335 rated CVSS 6.4. Exploitation could compromise the security of affected deployments. Organizations should apply vendor updates when available and monitor for exploitation.
Apply vendor patch. If patching is delayed: restrict network access and enable monitoring.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Weak password policy in Vikunja task management before 2.0.0 allows users to set trivially guessable passwords. PoC avai
Stored cross-site scripting (XSS) in Vikunja prior to version 2.0.0 allows authenticated attackers to steal authenticati
Vikunja before version 2.0.0 contains a path traversal vulnerability in its backup restoration function that fails to va
Vikunja is an open-source self-hosted task management platform. [CVSS 6.1 MEDIUM]
Business logic vulnerability in Vikunja task management platform before 2.1.0 allows incomplete resource cleanup, potent
Cross-tenant information disclosure in the self-hosted task manager Vikunja (0.24.0 through 2.3.0) lets a holder of any
Instance-wide data breach in Vikunja before 2.2.1 lets remote attackers exfiltrate and destroy every file attachment acr
Vikunja instances before 2.6.0 expose CalDAV BasicAuth endpoints (/dav, /.well-known, and /feeds) that are not covered b
Vikunja versions before 2.6.0 ship authentication endpoints under /api/v2 (login, register, password-reset, and OAuth to
Vikunja prior to 2.6.0 leaks the secret hash that backs a project's link shares through its single-share read endpoint,
Principal type confusion in Vikunja (versions 0.22.0-2.3.0) allows an authenticated low-privilege attacker to fully cont
Privilege escalation in Vikunja 2.3.0 allows a user who holds a narrowly scoped API token (permissions {"oauth":["author
EUVD-2026-14909
NVD
CVE.org
EPSS
Vulnrichment
GitHub
VulDB
Exploit-DB