Quick answers
- Is CVE-2026-54307 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-54307 being exploited in the wild.
- How severe is CVE-2026-54307?
- Critical severity, with a CVSS score of 9.6, published 23 June 2026.
- Which products and versions are affected?
- N8n < 1.123.55, >= 2.0.0-rc.0 < 2.25.7, >= 2.26.0 < 2.26.2; n8n (npm) SEMVER:introduced=0,fixed=1.123.55.
- Is there a fix for CVE-2026-54307?
- Yes. n8n (npm): upgrade to 1.123.55 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-54307 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-54307?
- Check whether you run N8n or n8n (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- n8n (npm): upgrade to 1.123.55 or later
npm install n8n@1.123.55
Technical details
An incorrect authorization vulnerability (CWE-863) exists in n8n's workflow sharing mechanism. The root cause is a partial enforcement of credential ownership checks within specific public API endpoints. An attacker with 'Editor' privileges on a shared workflow can exploit this by referencing and potentially exfiltrating credentials owned by other users. This requires the attacker to have an account on the instance and for workflow sharing to be enabled. The vulnerability is resolved in versions 1.123.55, 2.25.7, and 2.26.2 by implementing stricter ownership validation.
Affected products
- n8n-io n8n < 1.123.55, >= 2.0.0-rc.0 < 2.25.7, >= 2.26.0 < 2.26.2
Identifiers
- CVE-2026-54307
- GHSA-pmqw-72cg-wx85
Timeline
- 2026-06-10: advisory: GitHub Security Advisory published by n8n-io
- 2026-06-23: disclosed: CVE published to NVD dataset