| Component | n8n |
| Severity | medium (CVSS 6.5) |
| CVSS vector | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| Published (NVD) | 2026-08-20 |
| Last modified | 2026-09-01 |
| Affected versions | n8n < 1.123.69 n8n >= 2.33.0, < 2.33.4 n8n = 2.34.0 |
| Fixed in | 1.123.69, 2.33.4 |
| Weakness | CWE-209 |
| CISA KEV | not listed |
NVD description
n8n versions before 1.123.69, 2.33.4, and 2.34.1 contain an information disclosure vulnerability in the GraphQL node. When a GraphQL request fails at the connection level, the node re-throws the underlying HTTP client error unchanged instead of wrapping it in n8n's standard error type. That error contains the live request's headers, including a decrypted credential secret, which the execution engine persists verbatim. Any authenticated user able to read the resulting execution can retrieve the decrypted credential secret from the stored run data.
What to do
- Upgrade n8n to
1.123.69or later (or the patched release of your branch: 2.33.4). - Do not expose the component's API or UI to the internet without authentication in front of it.
Sources
- NVD: CVE-2026-77076
- https://github.com/n8n-io/n8n/security/advisories/GHSA-9fqj-7wc5-cwhx
- https://www.vulncheck.com/advisories/n8n-before-credential-leak-via-graphql-node-error
Read more
Other n8n CVEs
n8n versions before 1.123.80 contain a credential tampering vulnerability where duplicate node IDs bypass the workflow credential tamper gua...
n8n versions before 1.123.80, from 2.0.0 before 2.39.6, and from 2.40.0 before 2.40.1 contain a stored DOM cross-site scripting vulnerabilit...
n8n versions before 1.123.80, from 2.0.0 before 2.39.6, and from 2.40.0 before 2.40.1 contain a path traversal vulnerability in the Supabase...
n8n versions before 2.39.6 and 2.40.0 before 2.40.1 fail to validate credential ownership during inline agent node-tool introspection. Attac...
n8n versions before 1.123.80, from 2.0.0 before 2.39.6, and from 2.40.0 before 2.40.1 contain a filter injection vulnerability in the Supaba...
n8n versions before 1.123.80, from 2.0.0 before 2.39.6, and from 2.40.0 before 2.40.1 contain a NoSQL injection vulnerability in the MongoDB...