CVE-2026-33749

CRITICALNVD 9.09.0
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.0 under NVD CVSS v3. EPSS exploit probability: 0.3% (16th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 8.9 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-03-26) is not newer than that change (2026-06-17), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2026-15956 (ENISA EUVD) · GHSA-qfc3-hm4j-7q77 (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 9.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

n8n is an open source workflow automation platform. Prior to versions 1.123.27, 2.13.3, and 2.14.1, an authenticated user with permission to create or modify workflows could craft a workflow that produces an HTML binary data object without a filename. The /rest/binary-data endpoint served such responses inline on the n8n origin without Content-Disposition or Content-Security-Policy headers, allowing the HTML to render in the browser with full same-origin JavaScript access. By sending the resulting URL to a higher-privileged user, an attacker could execute JavaScript in the victim's authenticated session, enabling exfiltration of workflows and credentials, modification of workflows, or privilege escalation to admin. The issue has been fixed in n8n versions 1.123.27, 2.13.3, and 2.14.1. Users should upgrade to one of these versions or later to remediate the vulnerability. If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Limit workflow creation and editing permissions to fully trusted users only, and/or restrict network access to the n8n instance to prevent untrusted users from accessing binary data URLs. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

CVSS v3
9.0
EG Score
9.0CRITICALmedium confidence
EG Risk
41
EG Risk 41/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)
Severity90% × 45%
Impact severity (EG Severity): CVSS 9.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
16th
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 (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is its impact severity (EG Severity), not escalated.

EG Severity
9.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). 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 every mission impact level.CISA BOD 26-04: 60 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 every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 partial (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 25, 2026

Last Modified

June 17, 2026

Advisory Details (1)

Auto-updated Jul 28, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

XSS via Binary Data Inline HTML Rendering · Advisory · n8n-io/n8n · GitHub

https://github.com/n8n-io/n8n/security/advisories/GHSA-qfc3-hm4j-7q77

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmn8n @ 1.123.27 (fixes < 1.123.27)—ghsa
npmn8n @ 2.14.1 (fixes = 2.14.0)—ghsa
npmn8n @ 2.13.3 (fixes >= 2.0.0-rc.0, < 2.13.3)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
n8n2.14.0
  • every version up to 1.123.27: fixed in 1.123.27
  • 2.14.0 up to 2.14.1: fixed in 2.14.1
  • 2.0.0-rc.0 up to 2.13.3: fixed in 2.13.3
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 17× in last 7d / 60× 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 97 of 129 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. 3 repeat rows among the latest 100 are merged into the row they repeat. The 32 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-33749?
CVE-2026-33749 is a critical-severity vulnerability; its CVE record was published on March 25, 2026. n8n is an open source workflow automation platform. Prior to versions 1.123.27, 2.13.3, and 2.14.1, an authenticated user with permission to create or modify workflows could craft a workflow that produces an HTML binary data object without a filename. The /rest/binary-data endpoint served such…
When was the CVE record for CVE-2026-33749 published?
The CVE record for CVE-2026-33749 was published on March 25, 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-33749 actively exploited?
CVE-2026-33749 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (16th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-33749?
CVE-2026-33749 has a CVSS v3 base score of 9.0 (NVD).
How do I remediate CVE-2026-33749?
A fix for CVE-2026-33749 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-33749

Explore →

Is Your Infrastructure Affected by CVE-2026-33749?

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

Book a Demo →Browse All CVEs