---
id: "GHSA-pcr3-v5vr-qppf"
page: "https://infrastack.ai/live/GHSA-pcr3-v5vr-qppf"
kind: "vulnerability"
aliases: ["GHSA-pcr3-v5vr-qppf"]
title: "Per-User Credential Theft via Error-Workflow Execution Context Inheritance"
severity: "medium"
cvss: 5.1
epss: null
exploited: false
status: "open"
category: "ai-tooling"
products: [{"name": "n8n", "fixed": [">= 2.42.2"], "affected": "< 2.42.2", "ecosystem": "npm"}, {"name": "n8n", "fixed": [">= 2.41.5"], "affected": "< 2.41.5", "ecosystem": "npm"}]
ecosystems: ["npm"]
tags: ["ai-tooling", "n8n", "per-user-credentials", "self-hosted", "team-projects", "workflow-automation"]
not_affected_if: ["dynamic-credentials-disabled", "no-team-projects", "single-user-instance"]
published_at: "2026-10-14T09:43:37+00:00"
first_seen_at: "2026-11-09T22:53:26+00:00"
updated_at: "2026-11-09T22:56:58+00:00"
sources: [{"source": "ghsa-repo", "url": "https://github.com/n8n-io/n8n/security/advisories/GHSA-pcr3-v5vr-qppf", "first_seen_at": "2026-11-09T22:53:26+00:00"}]
exploit_sources: []
---

# Per-User Credential Theft via Error-Workflow Execution Context Inheritance

Link for people: https://infrastack.ai/live/GHSA-pcr3-v5vr-qppf (this .md is for agents)

n8n runs the error workflow named in a failed workflow's settings and passes it the failed run's execution context, including the identity of the user who started it. A project editor can point a colleague's workflow at an error workflow they own and read that user's per-user credential secrets.

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

## Affected

- npm:n8n affected < 2.42.2 fixed >= 2.42.2
- npm:n8n affected < 2.41.5 fixed >= 2.41.5

## How to check

- Confirm the n8n version with `n8n --version` or the npm package version in your install.
- Audit workflows for the `settings.errorWorkflow` field and look for unexpected values.
- Review team project memberships for editor access held by users who are not fully trusted.

## Fix

- n8n `2.42.2` (fixed line 2.42.x)
- n8n `2.41.5` (fixed line 2.41.x)

## Timeline

- 2026-11-09T22:53:26+00:00 ghsa-repo https://github.com/n8n-io/n8n/security/advisories/GHSA-pcr3-v5vr-qppf

## Documents

- [advisory] Vendor advisory: github.com https://github.com/n8n-io/n8n/security/advisories/GHSA-pcr3-v5vr-qppf

## From the sources

## Impact

When a workflow fails, n8n runs the workflow named in its error-workflow setting and hands it the failed run's execution context, including the carrier that binds the run to the user who started it. A project editor could point a colleague's workflow at an error workflow they own, inherit the colleague's identity in their own execution, and resolve that user's per-user credential secrets. The error workflow now receives only non-identity fields.

## Patches

The issue has been fixed in n8n versions 2.42.2 and 2.41.5. 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 team project memberships and remove editor access from any users who are not fully trusted.
- Review all active workflows and audit the `settings.errorWorkflow` field for unexpected values.
- Disable the dynamic credentials feature if it is not required.

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_