n8n | stable

n8n stable released on 22-04-2026


n8n stable is out now. It enforces credential access checks when nodes request dynamic parameter values (for example dropdowns and autocomplete), so nodes only receive data they are authorised to access and the risk of credential exposure is reduced.

Visit the n8n GitHub release page for full details and the linked commit that implements the fix.

What’s in this release

  • Enforces credential access checks in dynamic node parameter requests (dropdowns, autocomplete).
  • Fixes issue #28861; implemented in commit 9aadc28.
  • Hardens authorization around dynamic parameter fetching to reduce the risk of unauthorised credential exposure.

Upgrade notes

  • No reported breaking changes; administrators and self-hosted users should upgrade to 2.17.5 to ensure credential access controls are enforced.
  • Rollback is not expected for this patch-level security/hardening fix — after upgrading, quickly test flows that use dynamic node parameters or custom nodes that fetch credential-dependent values to confirm expected behaviour.

Share any comments or experience after upgrading, especially if you use custom nodes or rely on dynamic parameter values in your flows.

Related posts

Weekly Tech Digest | 06 Jul 2026

Stay updated with the latest in tech! This digest covers AI ethics, auto industry shifts, and the impact of politics on technology, exploring today's pressing issues.

wolfCOSE zero-allocation parsing in embedded C

wolfCOSE looks sensible only if you care about what your firmware actually has to carry. I like that, because on small targets the wrong crypto feature can cost more than the message itself, and there...

restic | v0.19.1

restic v0 19 1: safer FUSE mounts and mountpoint checks, robust backup source and exclude handling, clearer CLI JSON output, Windows SFTP deletion fixes