CVE-2026-54308

HIGHNVD 7.27.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.2 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 81% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
7.2
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.2Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

n8n is an open source workflow automation platform. Prior to 2.25.7 and 2.26.2, the MicrosoftAgent365Trigger and StripeTrigger node did not validate that inbound requests. As a result, an unauthenticated attacker who knows the webhook URL could submit a forged payload and cause the workflow to execute with attacker-controlled data. This vulnerability is fixed in 2.25.7 and 2.26.2.

CVSS v3
7.2
EG Score
7.2(medium)
EPSS
19.5%
KEV
Not listed

Published

June 16, 2026

Last Modified

June 26, 2026

Advisory Details (1)

Auto-updated Jun 23, 2026
Patch available. Sources: github.
github Patch Available

Missing Token Validation on Microsoft Agent 365 Trigger and Stripe Nodes · Advisory · n8n-io/n8n · GitHub

https://github.com/n8n-io/n8n/security/advisories/GHSA-jvc7-762p-3743

Vendor Advisories for CVE-2026-54308(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
n8n—2.25.7—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 21× in last 7d / 56× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-07-06 23:10 UTCEG score recompute
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-05 20:12 UTCEG score recompute
  7. 2026-07-05 08:42 UTCEG score recompute
  8. 2026-07-05 02:31 UTCEPSS rescore
  9. 2026-07-05 02:30 UTCEPSS rescore
  10. 2026-07-04 20:40 UTCEG score recompute
  11. 2026-07-04 09:10 UTCEG score recompute
  12. 2026-07-03 15:42 UTCEG score recompute
  13. 2026-07-03 04:11 UTCEG score recompute
  14. 2026-07-02 16:40 UTCEG score recompute
  15. 2026-07-02 05:10 UTCEG score recompute
  16. 2026-07-01 17:39 UTCEG score recompute
  17. 2026-07-01 15:07 UTCEPSS rescore
  18. 2026-07-01 06:08 UTCEG score recompute
  19. 2026-06-30 23:22 UTCEPSS rescore
  20. 2026-06-30 18:36 UTCEG score recompute
  21. 2026-06-30 07:04 UTCEG score recompute
  22. 2026-06-29 19:32 UTCEG score recompute
  23. 2026-06-29 14:06 UTCEPSS rescore
  24. 2026-06-29 14:06 UTCEPSS rescore
  25. 2026-06-29 08:02 UTCEG score recompute
Show 31 more
  1. 2026-06-28 20:30 UTCEG score recompute
  2. 2026-06-28 14:07 UTCEPSS rescore
  3. 2026-06-28 08:59 UTCEG score recompute
  4. 2026-06-28 04:56 UTCEPSS rescore
  5. 2026-06-28 04:56 UTCEPSS rescore
  6. 2026-06-27 21:29 UTCEG score recompute
  7. 2026-06-27 09:58 UTCEG score recompute
  8. 2026-06-27 03:08 UTCEPSS rescore
  9. 2026-06-26 22:27 UTCEG score recompute▲ 0.90
  10. 2026-06-26 03:53 UTCNVD updateCVSS v3 → 7.2 · severity → HIGH
  11. 2026-06-25 23:37 UTCEG score recompute
  12. 2026-06-25 13:49 UTCEPSS rescore
  13. 2026-06-25 00:47 UTCEG score recompute
  14. 2026-06-24 14:05 UTCEPSS rescore
  15. 2026-06-24 01:58 UTCEG score recompute▼ 0.90
  16. 2026-06-23 17:34 UTCNVD updateCVSS v3 → 6.3 · CVSS v4 → 6.3
  17. 2026-06-23 14:26 UTCEG score recompute
  18. 2026-06-23 02:54 UTCEG score recompute
  19. 2026-06-22 15:23 UTCEG score recompute
  20. 2026-06-22 03:49 UTCEG score recompute
  21. 2026-06-21 16:18 UTCEG score recompute
  22. 2026-06-21 04:11 UTCEG score recompute
  23. 2026-06-20 16:28 UTCEG score recompute
  24. 2026-06-20 04:56 UTCEG score recompute
  25. 2026-06-19 17:25 UTCEG score recompute
  26. 2026-06-19 05:23 UTCEG score recompute
  27. 2026-06-18 17:44 UTCEG score recompute
  28. 2026-06-18 06:03 UTCEG score recompute
  29. 2026-06-17 18:10 UTCEG score recompute
  30. 2026-06-17 06:40 UTCEG score recompute
  31. 2026-06-16 19:07 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-54308?
CVE-2026-54308 is a high vulnerability published on June 16, 2026. n8n is an open source workflow automation platform. Prior to 2.25.7 and 2.26.2, the MicrosoftAgent365Trigger and StripeTrigger node did not validate that inbound requests. As a result, an unauthenticated attacker who knows the webhook URL could submit a forged payload and cause the workflow to…
When was CVE-2026-54308 disclosed?
CVE-2026-54308 was first published in the National Vulnerability Database on June 16, 2026, with the most recent update on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54308 actively exploited?
CVE-2026-54308 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 19.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-54308?
CVE-2026-54308 has a CVSS v3 base score of 7.2 (NVD).
How do I remediate CVE-2026-54308?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54308, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-54308?

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

Start Free Scan →Browse All CVEs