CVE-2026-72763

HIGHPre-NVD 7.27.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 88% 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, secondary
Trending — 3 sources updated this week
7.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.2Exploit: None knownExposed: 0

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

n8n before 1.123.67, 2.31.5, and 2.32.1 validates credential-access only for a node's top-level credentials and not for credentials referenced inside an Execute Sub-workflow node's inline workflow JSON. A member with Editor access to a shared workflow (when workflow sharing is enabled) who knows a target credential's ID can reference that credential in the inline JSON; it passes save-time and runtime validation and resolves in the parent workflow's project context, allowing the attacker to use or exfiltrate credentials they are not permitted to access.

CVSS v3
7.2
EG Score
7.2(medium)
EG Risk
32(Track)
EG Risk 32/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity72% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
12%
KEV
Not listed

Published

August 11, 2026

Last Modified

August 11, 2026

Advisory Details (2)

Auto-updated Aug 11, 2026
Patch available. Sources: github.
generic

n8n before 1.123.67 Credential Exfiltration via Sub-Workflow | Advisories | VulnCheck

https://www.vulncheck.com/advisories/n8n-before-credential-exfiltration-via-sub-workflow
github Patch Available

Shared-Workflow Editor Can Exfiltrate Credentials via Inline Sub-Workflow JSON · Advisory · n8n-io/n8n · GitHub

https://github.com/n8n-io/n8n/security/advisories/GHSA-cj9h-qx8g-pq2g

Vendor Advisories for CVE-2026-72763(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—1.123.67—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 29× in last 7d / 45× 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-08-20 22:56 UTCEPSS rescore
  2. 2026-08-20 17:14 UTCGHSA enrichment
  3. 2026-08-20 05:55 UTCGHSA enrichment
  4. 2026-08-19 18:41 UTCEG score recompute
  5. 2026-08-19 18:41 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 06:26 UTCGHSA enrichment
  8. 2026-08-18 19:13 UTCEG score recompute
  9. 2026-08-18 19:13 UTCGHSA enrichment
  10. 2026-08-18 13:49 UTCEPSS rescore
  11. 2026-08-18 13:49 UTCEPSS rescore
  12. 2026-08-18 07:59 UTCGHSA enrichment
  13. 2026-08-17 20:44 UTCEG score recompute
  14. 2026-08-17 20:44 UTCGHSA enrichment
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-17 09:29 UTCGHSA enrichment
  17. 2026-08-16 22:15 UTCEG score recompute
  18. 2026-08-16 22:15 UTCGHSA enrichment
  19. 2026-08-16 14:56 UTCEPSS rescore
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 11:00 UTCEG score recompute
  22. 2026-08-16 11:00 UTCGHSA enrichment
  23. 2026-08-16 02:15 UTCEPSS rescore
  24. 2026-08-15 23:47 UTCGHSA enrichment
  25. 2026-08-15 12:33 UTCEG score recompute
Show 20 more
  1. 2026-08-15 12:33 UTCGHSA enrichment
  2. 2026-08-15 01:31 UTCEPSS rescore
  3. 2026-08-15 01:18 UTCGHSA enrichment
  4. 2026-08-14 14:04 UTCGHSA enrichment
  5. 2026-08-14 02:50 UTCEG score recompute
  6. 2026-08-14 02:50 UTCGHSA enrichment
  7. 2026-08-13 22:00 UTCEPSS rescore
  8. 2026-08-13 15:36 UTCGHSA enrichment
  9. 2026-08-13 04:22 UTCGHSA enrichment
  10. 2026-08-12 17:08 UTCEG score recompute
  11. 2026-08-12 17:08 UTCGHSA enrichment
  12. 2026-08-12 13:51 UTCEPSS rescore
  13. 2026-08-12 05:54 UTCGHSA enrichment
  14. 2026-08-11 18:39 UTCEG score recompute
  15. 2026-08-11 18:39 UTCGHSA enrichment
  16. 2026-08-11 18:16 UTCEG score recompute
  17. 2026-08-11 18:16 UTCGHSA enrichment
  18. 2026-08-11 13:25 UTCEG score recompute
  19. 2026-08-11 12:22 UTCEG score recompute
  20. 2026-08-11 12:22 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-72763?
CVE-2026-72763 is a high vulnerability published on August 11, 2026. n8n before 1.123.67, 2.31.5, and 2.32.1 validates credential-access only for a node's top-level credentials and not for credentials referenced inside an Execute Sub-workflow node's inline workflow JSON. A member with Editor access to a shared workflow (when workflow sharing is enabled) who knows a…
When was CVE-2026-72763 disclosed?
CVE-2026-72763 was first published in the National Vulnerability Database on August 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72763 actively exploited?
CVE-2026-72763 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 87.8% of all scored CVEs.
What is the CVSS score of CVE-2026-72763?
CVE-2026-72763 has a CVSS v3 base score of 7.2 (NVD).
How do I remediate CVE-2026-72763?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72763, 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-72763

Explore →

Is Your Infrastructure Affected by CVE-2026-72763?

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

Start Free Scan →Browse All CVEs