Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-54305: n8n is an open source workflow automation platform

42
This month
CRITICAL 9.9UPGRADE

CVE-2026-54305 is a critical-severity flaw (CVSS 9.9) affecting n8n. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 privat

Why this priority

  • Critical severity

A fixed release or distro patch exists.

Risk facts

CVSS score9.9 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance0.4% (top 69%)
CISA exploited listNo
WeaknessCWE-200, CWE-284
Published2026-06-23
Last modified2026-10-25
Publisher (CNA): GitHub, Inc. · Vendor: n8n

Share: LinkedIn · X · Reddit

Last updated 2026-10-25 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

n8n n8n UPGRADE
Affected: < 1.123.55 · >= 2.0.0 and < 2.25.7 · >= 2.26.0 and < 2.26.2
Fixed in: 1.123.55, 2.25.7, 2.26.2
Safe to downgrade to: a release before 2.0.0
1. Check installed version
npm ls n8n
2. UPGRADE to 1.123.55
npm install n8n@">=1.123.55"
3. If no update is available yet, DOWNGRADE to a release before 2.0.0
npm view n8n versions npm install n8n@"<2.0.0"
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-54305?

n8n: upgrade to 1.123.55, 2.25.7, 2.26.2. Exact commands for each OS are on this page.

Is CVE-2026-54305 being exploited?

CVE-2026-54305 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-54305 affect?

CVE-2026-54305 affects n8n. Severity is critical (CVSS 9.9). 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

How urgent is CVE-2026-54305?

Priority 42/100. Critical severity

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.