CVE-2026-77076: n8n · Generation of Error Message Containing Sensitive Information
Affects n8nSource CVE Database V5
Not known to be exploited · CVSS 7.1 High : upgrade to 1.123.69 soon.
Data as of 18 Nov 2026, 20:25 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.123.69, 2.34.1, 2.33.4
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 20 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| n8n-ion8n | Affected
| Fixed in
|
| n8n-ion8n | Affected
| Fixed in
|
| n8n-ion8n | Affected
| Fixed in
|
npmn8n-io/n8npkg:npm/n8n-io/n8nOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in n8n versions 1.123.69, 2.33.4, and 2.34.1. Users should upgrade to these or later versions to remediate the vulnerability. There is no indication that the vulnerability is mitigated in earlier versions or that no action is required.
Description
n8n versions prior to 1.123.69, 2.33.4, and 2.34.1 have an information disclosure vulnerability in the GraphQL node. When a GraphQL request fails at the connection level, the error message includes sensitive information such as decrypted credential secrets in the request headers. This sensitive data is stored verbatim in the execution engine's run data, accessible to any authenticated user who can read the execution results.