CVE-2026-54307
Cross-user credential access via Editor in shared n8n workflows.
Is CVE-2026-54307 being exploited?
Not confirmed. CVE-2026-54307 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.39% probability of exploitation in the next 30 days.
How severe is CVE-2026-54307?
CVE-2026-54307 is rated High with a CVSS score of 8.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-54307?
Yes. A fix has been recorded for CVE-2026-54307. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-54307 affect?
CVE-2026-54307 affects n8n (open-source) prior to 1.123.55, 2.25.7, 2.26.2. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-54307?
Upgrade to fixed versions: 1.123.55, 2.25.7, or 2.26.2
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Editor users can access credentials they don’t own via public API endpoints; credential theft risk across shared workflows.
Patch when possible
- affected< 1.123.55
- affected>= 2.0.0-rc.0 and < 2.25.7
- affected>= 2.26.0 and < 2.26.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.