CVE-2026-54305
Auth user can enumerate credentials and hijack OAuth tokens in n8n, enabling data exfiltration.
Is CVE-2026-54305 being exploited?
Not confirmed. CVE-2026-54305 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.37% probability of exploitation in the next 30 days.
How severe is CVE-2026-54305?
CVE-2026-54305 is rated High with a CVSS score of 8.9. 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-54305?
Yes. A fix has been recorded for CVE-2026-54305. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-54305 affect?
CVE-2026-54305 affects n8n (open source) prior to v1.123.55, v2.25.7, v2.26.2. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-54305?
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.
Authenticated attacker can enumerate credentials, hijack tokens, overwrite tokens or revoke them, causing data loss and persistent integration takeover.
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.