CVE-2026-33336

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 1.2% (67th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Elevated

Also known asEUVD-2026-14911 (ENISA EUVD)Source: ENISA EUVD

8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 1.2%CVSS: 8.8Exploit: No code on recordExposed services: Not assessed

The CVE record names the fixed release — apply it.

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.

Root cause

Two misconfigurations combine to create this vulnerability:

  • 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.).
  • 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:
  • ` links (without target="_blank")
  • window.location assignments
  • HTTP redirects
  • tags

Attack scenario

  • The attacker is a normal user on the same Vikunja instance (e.g., a member of a shared project).
  • The attacker creates or edits a project description or task description containing a standard HTML link, e.g.: Click here for the updated design spec
  • 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.
  • The victim uses Vikunja Desktop and clicks the link.
  • Because no will-navigate handler exists, the BrowserWindow navigates to https://evil.example/exploit in the same renderer process.
  • The attacker's page now executes in a context with nodeIntegration: true and runs: require('child_process').exec('id > /tmp/pwned');
  • Arbitrary commands execute as the victim's OS user.

Impact

Full 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.

Proof of concept

  • Set up a Vikunja instance with two users sharing a project.
  • As the attacker user, edit a project description to include: Meeting notes
  • Host poc.html with: require('child_process').exec('calc.exe')`
  • As the victim, open the project in Vikunja Desktop and click the link.
  • calc.exe (or any other command) executes on the victim's machine.

Credits

This vulnerability was found using GitHub Security Lab Taskflows.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
56
EG Risk 56/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
1.2%
EPSS %ILE
67th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
1.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

March 24, 2026

Last Modified

June 17, 2026

Advisory Details (2)

Auto-updated Aug 2, 2026
Fix named in the CVE record. Sources: github.
Web page

Vikunja 2.2.0: Ten security fixes, Gantt overhaul, and task duplication

https://vikunja.io/changelog/vikunja-v2.2.0-was-released
GitHub advisoryMentions a patch (unverified)

Remote Code Execution via same-window navigation in Vikunja Desktop · Advisory · go-vikunja/vikunja · GitHub

https://github.com/go-vikunja/vikunja/security/advisories/GHSA-83w9-9jf6-88vf

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 39× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 96 of 108 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 100 are merged into the row they repeat. The 12 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:34 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  2. 2026-10-31 16:32 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  3. 2026-10-30 16:34 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  4. 2026-10-29 16:33 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  5. 2026-10-28 16:32 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  6. 2026-10-27 18:01 UTCEG score recompute
  7. 2026-10-27 16:31 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  8. 2026-10-26 16:31 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  9. 2026-10-25 16:32 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  10. 2026-10-25 14:34 UTCEG score recompute
  11. 2026-10-24 16:32 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  12. 2026-10-23 16:31 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  13. 2026-10-22 16:34 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  14. 2026-10-21 16:32 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  15. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  16. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  17. 2026-10-19 14:08 UTCEG score recompute
  18. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  19. 2026-10-18 03:46 UTCEG score recompute
  20. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  21. 2026-10-16 16:41 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  22. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  23. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  24. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  25. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.9% · 59th percentile
Show 71 more
  1. 2026-10-12 15:47 UTCEG score recompute
  2. 2026-10-11 19:55 UTCEG score recompute
  3. 2026-10-11 17:09 UTCEG score recompute
  4. 2026-10-11 14:36 UTCEG score recompute
  5. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  6. 2026-10-11 06:25 UTCOSV refresh
  7. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  8. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  9. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  10. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  11. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  12. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  13. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  14. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  15. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  16. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  17. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  18. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  19. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  20. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  21. 2026-09-21 18:49 UTCOSV refresh
  22. 2026-09-20 20:15 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  23. 2026-09-18 19:28 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  24. 2026-09-17 19:30 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  25. 2026-09-16 14:08 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  26. 2026-09-16 05:15 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  27. 2026-09-15 03:11 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  28. 2026-09-13 16:47 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  29. 2026-09-12 15:01 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  30. 2026-09-11 14:53 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  31. 2026-09-11 09:37 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  32. 2026-09-10 09:34 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  33. 2026-09-08 22:00 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  34. 2026-09-07 16:01 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  35. 2026-09-06 13:47 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  36. 2026-09-04 05:06 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  37. 2026-09-02 15:38 UTCOSV refresh
  38. 2026-09-02 14:11 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  39. 2026-09-01 13:53 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  40. 2026-09-01 04:39 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  41. 2026-08-30 19:17 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  42. 2026-08-30 01:22 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  43. 2026-08-28 21:41 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  44. 2026-08-27 14:25 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  45. 2026-08-26 14:46 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  46. 2026-08-25 13:49 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  47. 2026-08-24 14:17 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  48. 2026-08-23 00:19 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  49. 2026-08-21 23:49 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  50. 2026-08-20 22:55 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  51. 2026-08-19 17:03 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  52. 2026-08-18 13:48 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  53. 2026-08-17 13:47 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  54. 2026-08-16 14:56 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  55. 2026-08-16 10:38 UTCEG score recompute
  56. 2026-08-16 02:14 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  57. 2026-08-15 01:30 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  58. 2026-08-14 06:51 UTCEG score recompute
  59. 2026-08-13 22:00 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  60. 2026-08-12 21:30 UTCEG score recompute
  61. 2026-08-12 13:50 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  62. 2026-08-11 21:08 UTCEG score recompute
  63. 2026-08-11 04:10 UTCEG score recompute
  64. 2026-08-11 00:00 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
  65. 2026-08-09 19:30 UTCEG score recompute
  66. 2026-08-09 13:46 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
  67. 2026-08-09 06:27 UTCEG score recompute
  68. 2026-08-08 16:37 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
  69. 2026-08-07 16:46 UTCEG score recompute
  70. 2026-08-06 19:04 UTCEG score recompute
  71. 2026-08-06 13:46 UTCEPSS rescoreEPSS 1.1% · 62nd percentile

Frequently asked(5)

What is CVE-2026-33336?
CVE-2026-33336 is a high-severity vulnerability; its CVE record was published on March 24, 2026. 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…
When was the CVE record for CVE-2026-33336 published?
The CVE record for CVE-2026-33336 was published on March 24, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2026-33336 actively exploited?
CVE-2026-33336 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.2% probability of exploitation in the next 30 days (67th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-33336?
CVE-2026-33336 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-33336?
The CVE record for CVE-2026-33336 names the fix: "Version 2.2.0 patches the issue."

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-33336

Explore →

Is Your Infrastructure Affected by CVE-2026-33336?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.