CVE-2026-54303

MEDIUMNVD 5.45.4—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.4 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 93% 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
5.4
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.4Exploit: 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.24.0, an endpoint in the Meta and Microsoft Teams trigger nodes reflects a query parameter into the HTTP response without sanitization or Content-Security-Policy headers, enabling reflected XSS in the n8n origin when a logged-in user visits a crafted URL. This vulnerability is fixed in 2.24.0.

CVSS v3
5.4
EG Score
5.4(medium)
EPSS
7.4%
KEV
Not listed

Published

June 16, 2026

Last Modified

June 25, 2026

Advisory Details (1)

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

Reflected XSS via Facebook, WhatsApp, and Microsoft Teams Trigger Webhook Verification Endpoints · Advisory · n8n-io/n8n · GitHub

https://github.com/n8n-io/n8n/security/advisories/GHSA-h86q-fx34-gfjr

Vendor Advisories for CVE-2026-54303(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.24.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 17× in last 7d / 47× 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 22:57 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 12:31 UTCEG score recompute
  7. 2026-07-05 02:31 UTCEPSS rescore
  8. 2026-07-05 02:30 UTCEPSS rescore
  9. 2026-07-04 13:03 UTCEG score recompute
  10. 2026-07-04 06:31 UTCEPSS rescore
  11. 2026-07-04 06:31 UTCEPSS rescore
  12. 2026-07-03 13:44 UTCEG score recompute
  13. 2026-07-02 11:13 UTCEG score recompute
  14. 2026-07-01 15:07 UTCEPSS rescore
  15. 2026-07-01 11:27 UTCEG score recompute
  16. 2026-06-30 23:22 UTCEPSS rescore
  17. 2026-06-30 12:06 UTCEG score recompute
  18. 2026-06-29 14:06 UTCEPSS rescore
  19. 2026-06-29 14:06 UTCEPSS rescore
  20. 2026-06-29 12:18 UTCEG score recompute
  21. 2026-06-28 14:07 UTCEPSS rescore
  22. 2026-06-28 13:00 UTCEG score recompute
  23. 2026-06-28 04:56 UTCEPSS rescore
  24. 2026-06-28 04:56 UTCEPSS rescore
  25. 2026-06-27 13:43 UTCEG score recompute
Show 22 more
  1. 2026-06-27 03:08 UTCEPSS rescore
  2. 2026-06-26 14:25 UTCEG score recompute▼ 1.40
  3. 2026-06-25 19:49 UTCNVD updateCVSS v3 → 5.4
  4. 2026-06-25 15:06 UTCEG score recompute
  5. 2026-06-25 13:49 UTCEPSS rescore
  6. 2026-06-24 15:49 UTCEG score recompute
  7. 2026-06-24 14:05 UTCEPSS rescore
  8. 2026-06-23 16:31 UTCEG score recompute▼ 0.80
  9. 2026-06-23 15:45 UTCMITRE cvelistV5CVSS v3 → 6.8 · CVSS v4 → 6.8
  10. 2026-06-23 04:09 UTCEG score recompute
  11. 2026-06-22 15:48 UTCEG score recompute
  12. 2026-06-22 03:24 UTCEG score recompute
  13. 2026-06-21 14:23 UTCEG score recompute
  14. 2026-06-21 02:04 UTCEG score recompute
  15. 2026-06-20 13:43 UTCEG score recompute
  16. 2026-06-20 01:24 UTCEG score recompute
  17. 2026-06-19 12:40 UTCEG score recompute
  18. 2026-06-19 00:07 UTCEG score recompute
  19. 2026-06-18 11:48 UTCEG score recompute
  20. 2026-06-17 23:27 UTCEG score recompute
  21. 2026-06-17 11:04 UTCEG score recompute
  22. 2026-06-16 22:44 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-54303?
CVE-2026-54303 is a medium vulnerability published on June 16, 2026. n8n is an open source workflow automation platform. Prior to 2.24.0, an endpoint in the Meta and Microsoft Teams trigger nodes reflects a query parameter into the HTTP response without sanitization or Content-Security-Policy headers, enabling reflected XSS in the n8n origin when a logged-in user…
When was CVE-2026-54303 disclosed?
CVE-2026-54303 was first published in the National Vulnerability Database on June 16, 2026, with the most recent update on June 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54303 actively exploited?
CVE-2026-54303 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 7.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-54303?
CVE-2026-54303 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2026-54303?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54303, 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-54303

Explore →

Is Your Infrastructure Affected by CVE-2026-54303?

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

Start Free Scan →Browse All CVEs