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

Metadata schema choices for content libraries

Structured metadata only works when it matches how people actually retrieve content. I have seen neat schemas fail as soon as the library meets real records, and tarot makes the problem obvious. If...

Federation trade-offs in self-hosted social feeds

Federation looks tidy until you let it touch the edges, and then the odd cases arrive fast. I prefer self-hosted social feeds that stay explicit about what is local, what is remote, and what should...

FireAvert Z-Wave stove shutoffs for offline safety

FireAvert’s setup does the part that matters without asking Home Assistant to babysit it, which is exactly how I want stove protection to behave. The Home Assistant Z-Wave stove shutoffs badge is...