CVE-2026-77076: n8n before 1.123.69 Credential Leak via GraphQL Node Error
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
n8nto a version that resolves this vulnerability.Fixed in 1.123.69 - Upgrade
Upgrade
n8nto a version that resolves this vulnerability.Fixed in 2.33.4 - Upgrade
Upgrade
n8nto a version that resolves this vulnerability.Fixed in 2.34.1 - Operational
Rotate any decrypted credential secrets that may have been exposed in stored run data or in GraphQL node error contents for affected n8n versions (before 1.123.69, 2.33.4, and 2.34.1).
Event History
Frequently Asked Questions
Which n8n releases address this issue?
The issue affects versions before 1.123.69, 2.33.4, and 2.34.1. Upgrade to the applicable listed release or a later version.
Who can retrieve the exposed credential secret?
An authenticated user who can read the execution generated by a GraphQL node connection-level failure can retrieve the decrypted credential secret from the persisted run data.
What conditions are required for disclosure?
A GraphQL request must fail at the connection level. The resulting underlying HTTP client error is stored unchanged and includes the live request headers containing the decrypted credential secret.