GHSA-hv7x-3x78-gx53 — n8n
HIGHGHSA-hv7x-3x78-gx53 is a high-severity (CVSS 7.4) CWE-863 vulnerability in n8n. A fix is available for n8n — see the affected versions and patch details below.
n8n: Wrong OAuth Scope On Evaluations Test Run Creation Endpoint
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-hv7x-3x78-gx53.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-hv7x-3x78-gx53 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 383,485 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
n8nnpmDescription
Impact
The POST /workflows/{workflowId}/test-runs/new endpoint authorized access using workflow:read rather than workflow:execute. An authenticated user with read-only access to a workflow could trigger a real evaluation test run, causing the workflow to execute via the internal workflow runner. This could result in unintended outbound API calls, data mutations, or other side effects in downstream systems connected to the workflow.
This issue primarily affects instances where the Evaluations feature is in use and where users may have workflow:read access without workflow:execute access, such as deployments using RBAC project roles.
Patches
The issue has been fixed in n8n versions 1.123.55, 2.25.7, and 2.26.2. Users should upgrade to one of these versions or later to remediate the vulnerability.
Workarounds
If upgrading is not immediately possible, administrators should consider the following temporary mitigations:
- Restrict workflow access to fully trusted users only.
- Audit project role assignments and limit
workflow:readaccess on sensitive workflows to users who should also be permitted to execute them.
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | n8n | all versions | 1.123.55npm install n8n@1.123.55 |
| 📦npm | n8n | ≥ 2.26.0&&< 2.26.2 | 2.26.2npm install n8n@2.26.2 |
| 📦npm | n8n | ≥ 2.0.0-rc.0&&< 2.25.7 | 2.25.7npm install n8n@2.25.7 |
Affected Products
n8nn8nDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for n8n, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update n8n to 1.123.55 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hv7x-3x78-gx53 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is GHSA-hv7x-3x78-gx53 in your dependencies?
Find it across npm, including transitive dependencies.