n8n is a workflow automation platform. In n8n versions before 1.123.76, 2.37.7, and 2.38.2, the source control push endpoint derived the set of files to push from the file paths and status supplied in the client request payload instead of from the server-side status computed for the requesting user. An authenticated project-scoped user (e.g., a project admin) could therefore reference files belonging to projects they have no access to and push a deletion of those projects' workflows and credentials, resulting in cross-project data destruction. Exploitation requires the Source Control (Environments) enterprise feature to be licensed, enabled, and connected to a remote repository. The issue is fixed in 1.123.76, 2.37.7, and 2.38.2.
CVE-2026-92588
Score 4.4 from GitHub Security Advisory published 2026-09-17. a secondary CVSS source baseline 4.4; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.4
- EG Score
- 4.4(high)
- EG Risk
- 20(Track)EG Risk 20/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 computedSeverity44% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 9%
- KEV
- Not listed
Published
September 16, 2026
Last Modified
September 17, 2026
Advisory Details (2)
Auto-updated Sep 16, 2026n8n before 1.123.76 Improper Authorization via Source Control Push | Advisories | VulnCheck
https://www.vulncheck.com/advisories/n8n-before-1.123.76-improper-authorization-via-source-control-pushImproper Authorization in Source Control Push Allows Cross-Project Workflow and Credential Deletion · Advisory · n8n-io/n8n · GitHub
https://github.com/n8n-io/n8n/security/advisories/GHSA-hvrx-jc5j-pg3wVendor Advisories for CVE-2026-92588(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 16× in last 7d / 16× 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.
- 2026-09-20 20:16 UTCEPSS rescore
- 2026-09-20 15:02 UTCEG score recompute
- 2026-09-20 15:02 UTCGHSA enrichment
- 2026-09-19 15:09 UTCEG score recompute
- 2026-09-19 15:08 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 15:16 UTCEG score recompute
- 2026-09-18 15:16 UTCGHSA enrichment
- 2026-09-17 19:32 UTCEPSS rescore
- 2026-09-17 15:23 UTCEG score recompute
- 2026-09-17 15:23 UTCGHSA enrichment
- 2026-09-17 14:49 UTCEG score recompute
- 2026-09-17 14:49 UTCGHSA enrichment
- 2026-09-16 22:25 UTCEG score recompute
- 2026-09-16 21:54 UTCEG score recompute
- 2026-09-16 21:54 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-639
Frequently asked(5)
What is CVE-2026-92588?
When was CVE-2026-92588 disclosed?
Is CVE-2026-92588 actively exploited?
What is the CVSS score of CVE-2026-92588?
How do I remediate CVE-2026-92588?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-92588
Is Your Infrastructure Affected by CVE-2026-92588?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.