CVE-2026-92587
MEDIUMDescription
n8n is a workflow automation platform. In versions before 1.123.76, 2.37.7, and 2.38.2, the Git node validated a relative remote URL against the configured repositoryPath but then invoked git with that path as its working directory; git walked up to the enclosing repository's top level and resolved the same relative URL from there. An authenticated user (member) who nested the repository one level below the configured path could therefore make an identical URL string pass the file-access check while git resolved it outside the sandbox. A subsequent fetch or pull read a git repository outside N8N_RESTRICT_FILE_ACCESS_TO and merged its objects into the user's own repository, where their contents could be read back. The issue is fixed in n8n 1.123.76, 2.37.7, and 2.38.2, which resolve the remote reference from the directory git actually operates in before applying the sandbox check. As a workaround, the Git node can be disabled by adding n8n-nodes-base.git to NODES_EXCLUDE.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 8% of all known CVEs.
References
Related Vulnerabilities
Other CWE-426 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2015-0096 | High | 9.3 | 71% | - | - |
| CVE-2016-10009 | High | 7.3 | 37% | - | Fix |
| CVE-2016-0016 | High | 7.8 | 30% | - | - |
| CVE-2012-1854 | High | 7.8 | 21% | KEV | - |
| CVE-2018-12589 | High | 7.8 | 20% | - | - |
| CVE-2022-22047 | High | 7.8 | 19% | KEV | Fix |
Common questions
How do I fix CVE-2026-92587?
No published fix for CVE-2026-92587 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-92587 being actively exploited?
Not that we know of. CVE-2026-92587 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.18% is the estimated probability that it will be exploited in the next 30 days. That is higher than 8% of all scored CVEs.
How severe is CVE-2026-92587?
CVE-2026-92587 has a CVSS v3 base score of 5.0, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-92587
Markdown
[](https://tridentstack.com/cve/CVE-2026-92587)HTML
<a href="https://tridentstack.com/cve/CVE-2026-92587"><img src="https://tridentstack.com/cve/badge/CVE-2026-92587.svg" alt="CVE-2026-92587"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-16.