---
id: "GHSA-h59h-rf6m-7jp5"
page: "https://infrastack.ai/live/GHSA-h59h-rf6m-7jp5"
kind: "vulnerability"
aliases: ["GHSA-h59h-rf6m-7jp5"]
title: "Workflow Activation Allows Trigger Nodes to Use Credentials the Publisher Cannot Access"
severity: "medium"
cvss: 5.3
epss: null
exploited: false
status: "open"
category: "ai-tooling"
products: [{"name": "n8n", "fixed": ["1.123.96"], "affected": "< 1.123.96", "ecosystem": "npm"}, {"name": "n8n", "fixed": ["3.2.2"], "affected": "< 3.2.2", "ecosystem": "npm"}, {"name": "n8n", "fixed": ["2.48.3"], "affected": "< 2.48.3", "ecosystem": "npm"}, {"name": "n8n", "fixed": ["2.47.6"], "affected": "< 2.47.6", "ecosystem": "npm"}]
ecosystems: ["npm"]
tags: ["ai-tooling", "github", "gitlab", "n8n", "self-hosted", "webhooks"]
not_affected_if: ["single-user", "trusted-users-only"]
published_at: "2026-11-13T10:56:14+00:00"
first_seen_at: "2026-11-13T11:06:24+00:00"
updated_at: "2026-11-13T11:06:57+00:00"
sources: [{"source": "ghsa-repo", "url": "https://github.com/n8n-io/n8n/security/advisories/GHSA-h59h-rf6m-7jp5", "first_seen_at": "2026-11-13T11:06:24+00:00"}]
exploit_sources: []
---

# Workflow Activation Allows Trigger Nodes to Use Credentials the Publisher Cannot Access

Link for people: https://infrastack.ai/live/GHSA-h59h-rf6m-7jp5 (this .md is for agents)

When a workflow is activated, n8n registers its trigger nodes using the credentials set on them without checking the publisher may use those credentials. A member who knows another user's credential ID can activate a workflow that uses it, so n8n creates or deletes webhooks on the connected service with that credential's privileges and receives events from resources the member chooses.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- npm:n8n affected < 1.123.96 fixed 1.123.96
- npm:n8n affected < 3.2.2 fixed 3.2.2
- npm:n8n affected < 2.48.3 fixed 2.48.3
- npm:n8n affected < 2.47.6 fixed 2.47.6

## How to check

- Audit active workflows for trigger nodes that use credentials owned by another user.
- Review webhooks registered on connected services such as GitLab and GitHub for unexpected entries.
- Check the installed n8n version against the fixed versions.

## Fix

- `n8n` 1.123.96
- `n8n` 2.47.6
- `n8n` 2.48.3
- `n8n` 3.2.2

## Timeline

- 2026-11-13T11:06:24+00:00 ghsa-repo https://github.com/n8n-io/n8n/security/advisories/GHSA-h59h-rf6m-7jp5

## Documents

- [advisory] Maintainer's advisory: github.com https://github.com/n8n-io/n8n/security/advisories/GHSA-h59h-rf6m-7jp5

## From the sources

## Impact

When a workflow was activated, n8n registered its trigger nodes with the connected services using the credentials set on those nodes. Activation did not check that the user publishing the workflow had access to those credentials. A member who knew the ID of another user's credential could activate a workflow whose trigger used it. n8n then created or deleted webhooks on the connected service with that credential's privileges, and delivered events from resources the member chose to the member's workflow.

## Patches

The issue has been fixed in n8n versions 1.123.96, 2.47.6, 2.48.3 and 3.2.2. Users should upgrade to one of these versions or later to remediate the vulnerability.

## Workarounds

If upgrading is not immediately possible, administrators should consider the following temporary mitigations:
- Restrict n8n instance access to fully trusted users only.
- Audit active workflows for trigger nodes that use credentials owned by another user, and deactivate any that are not expected.
- Review the webhooks registered on connected services such as GitLab and GitHub, and remove any that are not expected.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_