Skip to main content
VulnerabilityPublished

CVE-2026-54305: n8n · Information Exposure

Affects n8nSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.9 High · fixed in 2.26.2 : patch n8n soon.

Data as of 5 Nov 2026, 23:24 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Jun 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 5 Nov 2026.

What to do

Upgrade n8n and n8n-io/n8n to 2.26.2, 2.25.7 or 1.123.55.

Affected software

ProductAffectedFixed in
n8n-ion8nAffected
  • >=2.26.0 <2.26.2
Fixed in
  • 2.26.2
n8n-ion8nAffected
  • >=2.0.0-rc.0 <2.25.7
Fixed in
  • 2.25.7
n8n-ion8nAffected
  • <1.123.55
Fixed in
  • 1.123.55
GitHubn8n-io/n8npkg:github/n8n-io/n8nOther threatsAffected
  • <1.123.55
  • <2.25.7
  • <2.26.2
Fixed in
  • 1.123.55
  • 2.25.7
  • 2.26.2

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

AI-suggested

This vulnerability is fixed in n8n versions 1.123.55, 2.25.7, and 2.26.2. Users should upgrade to at least these versions to remediate the issue. No other mitigation or temporary workaround is indicated in the available data.

Description

n8n is an open source workflow automation platform. Prior to 1.123.55, 2.25.7, and 2.26.2, three EE endpoints used by the Dynamic Credentials feature accepted any authenticated n8n session without performing per-resource ownership or scope checks on the target workflow or credential. An authenticated user with no project membership or credential sharing relationship could enumerate credential identifiers, names, and types referenced by any private workflow in the instance, initiate an OAuth authorization flow against another user's credential to overwrite its stored tokens with tokens bound to an account they control, or revoke another user's stored credential tokens entirely. Workflows relying on a hijacked credential would subsequently execute under the attacker's OAuth identity, enabling data exfiltration to attacker-controlled external services and persistent takeover of integrations. Token revocation would break affected workflows. This vulnerability is fixed in 1.123.55, 2.25.7, and 2.26.2.

References

Community reviews

Loading reviews…