Skip to main content
VulnerabilityPublished

CVE-2026-59209: n8n · Insufficiently Protected Credentials

Affects n8nSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.1 High · fixed in 2.28.1 : patch n8n soon.

Data as of 21 Nov 2026, 17:35 UTC

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.28.1, 2.27.4, 1.123.61
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 21 Nov 2026.

What to do

Upgrade n8n and n8n-io/n8n to 2.28.1, 2.27.4 or 1.123.61.

Affected software

ProductAffectedFixed in
n8n-ion8nAffected
  • >=2.28.0 <2.28.1
Fixed in
  • 2.28.1
n8n-ion8nAffected
  • >=2.0.0-rc.0 <2.27.4
Fixed in
  • 2.27.4
n8n-ion8nAffected
  • <1.123.61
Fixed in
  • 1.123.61
GitHubn8n-io/n8npkg:github/n8n-io/n8nOther threatsAffected
  • <1.123.61
  • <2.27.4
  • <2.28.1
Fixed in
  • 1.123.61
  • 2.27.4
  • 2.28.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade n8n to version 1.123.61, 2.27.4, or 2.28.1 or later, where this vulnerability is fixed. Patch status is confirmed by the version information in the advisory. No additional mitigation steps are indicated.

Description

n8n versions prior to 1.123.61, 2.27.4, and 2.28.1 contain a vulnerability where an authenticated user with editor access to a shared workflow can access credential-populated headers via the $request object in an HTTP Request node's pagination expression. This exposure allows the user to read and exfiltrate sensitive credentials. The issue is addressed in versions 1.123.61, 2.27.4, and 2.28.1.

References

Community reviews

Loading reviews…