CVE-2026-21894

MEDIUMNVD 6.56.5
EchelonGraph scoreMEDIUM confidence

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

Score 6.5 from GitHub Security Advisory (severity: MODERATE) published 2026-01-07. NVD baseline CVSS 6.5; sources differ by 0.0.

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

Also known asEUVD-2026-1185 (ENISA EUVD) · GHSA-jf52-3f2h-h9j5 (GitHub Security Advisories)Source: ENISA EUVD

6.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 6.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

n8n is an open source workflow automation platform. In versions from 0.150.0 to before 2.2.2, an authentication bypass vulnerability in the Stripe Trigger node allows unauthenticated parties to trigger workflows by sending forged Stripe webhook events. The Stripe Trigger creates and stores a Stripe webhook signing secret when registering the webhook endpoint, but incoming webhook requests were not verified against this secret. As a result, any HTTP client that knows the webhook URL could send a POST request containing a matching event type, causing the workflow to execute as if a legitimate Stripe event had been received. This issue affects n8n users who have active workflows using the Stripe Trigger node. An attacker could potentially fake payment or subscription events and influence downstream workflow behavior. The practical risk is reduced by the fact that the webhook URL contains a high-entropy UUID; however, authenticated n8n users with access to the workflow can view this webhook ID. This issue has been patched in version 2.2.2. A temporary workaround for this issue involves users deactivating affected workflows or restricting access to workflows containing Stripe Trigger nodes to trusted users only.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
29
EG Risk 29/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)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 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.5%
EPSS %ILE
40th
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 (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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

January 8, 2026

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Aug 6, 2026
Patch available. Sources: github_commit, github_pr, github.
GitHub advisoryMentions a patch (unverified)

Missing Stripe-Signature Verification Allows Unauthenticated Forged Webhooks · Advisory · n8n-io/n8n · GitHub

https://github.com/n8n-io/n8n/security/advisories/GHSA-jf52-3f2h-h9j5
GitHub pull request

fix(Stripe Trigger Node): Add Stripe signature verification

Fix merged in n8n-io/n8n PR #22764 on 2025-12-22 — awaiting tagged release

https://github.com/n8n-io/n8n/pull/22764
GitHub commit

commit a61a5991093c (n8n-io/n8n)

Fix landed in n8n-io/n8n commit a61a5991093c — awaiting tagged release

https://github.com/n8n-io/n8n/commit/a61a5991093c41863506888336e808ac1eff8d59

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmn8n @ 2.2.2 (fixes >= 0.150.0, < 2.2.2)—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
n8n—
  • 0.150.0 up to 2.2.2: fixed in 2.2.2
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 41× 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 99 of 198 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 99 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-21894?
CVE-2026-21894 is a medium-severity vulnerability; its CVE record was published on January 8, 2026. n8n is an open source workflow automation platform. In versions from 0.150.0 to before 2.2.2, an authentication bypass vulnerability in the Stripe Trigger node allows unauthenticated parties to trigger workflows by sending forged Stripe webhook events. The Stripe Trigger creates and stores a Stripe…
When was the CVE record for CVE-2026-21894 published?
The CVE record for CVE-2026-21894 was published on January 8, 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-21894 actively exploited?
CVE-2026-21894 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (40th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-21894?
CVE-2026-21894 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-21894?
A fix for CVE-2026-21894 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-21894

Explore →

Is Your Infrastructure Affected by CVE-2026-21894?

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

Book a Demo →Browse All CVEs