---
id: "GHSA-v9cx-v88r-42vw"
page: "https://infrastack.ai/live/GHSA-v9cx-v88r-42vw"
kind: "vulnerability"
aliases: ["GHSA-v9cx-v88r-42vw"]
title: "Credential Permission Check Skips Nodes Whose Default Parameters Are Omitted"
severity: "medium"
cvss: 5.1
epss: null
exploited: false
status: "open"
category: "ai-tooling"
products: [{"name": "n8n", "fixed": [">= 1.123.85"], "affected": "< 1.123.85", "ecosystem": "npm"}, {"name": "n8n", "fixed": [">= 2.44.1"], "affected": "< 2.44.1", "ecosystem": "npm"}, {"name": "n8n", "fixed": [">= 2.43.5"], "affected": "< 2.43.5", "ecosystem": "npm"}]
ecosystems: ["npm"]
tags: ["ai-tooling", "credentials", "n8n", "self-hosted", "workflows"]
not_affected_if: ["single-user-instance", "trusted-users-only"]
published_at: "2026-10-14T09:43:43+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-v9cx-v88r-42vw", "first_seen_at": "2026-11-09T22:53:26+00:00"}]
exploit_sources: []
---

# Credential Permission Check Skips Nodes Whose Default Parameters Are Omitted

Link for people: https://infrastack.ai/live/GHSA-v9cx-v88r-42vw (this .md is for agents)

n8n checks that a workflow's owner may use each credential it references, but the check misses credential slots whose default values are not stored, so a member can run a workflow that uses a credential they cannot access. The decrypted credential can then be sent to a destination the member chooses.

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

## Affected

- npm:n8n affected < 1.123.85 fixed >= 1.123.85
- npm:n8n affected < 2.44.1 fixed >= 2.44.1
- npm:n8n affected < 2.43.5 fixed >= 2.43.5

## How to check

- Check the installed version with `npm ls n8n` or the n8n version in the instance settings.
- Confirm whether members have accounts on the instance who should not reach every credential, by reviewing credential sharing in the n8n UI.
- Review execution logs for credential use by member accounts.

## Fix

- Upgrade n8n 1.x to `1.123.85` or later.
- Upgrade n8n 2.43.x to `2.43.5` or later.
- Upgrade n8n 2.44.x to `2.44.1` or later.

## Timeline

- 2026-11-09T22:53:26+00:00 ghsa-repo https://github.com/n8n-io/n8n/security/advisories/GHSA-v9cx-v88r-42vw

## Documents

- [advisory] Vendor advisory: github.com https://github.com/n8n-io/n8n/security/advisories/GHSA-v9cx-v88r-42vw

## From the sources

## Impact

Before a workflow runs, n8n checks that its owner may use every credential the workflow references. That check only looked at credential slots it considered active, and it decided which slots were active from the parameters as stored, where default values are omitted. At execution the defaults are restored and the node uses the credential. A member can therefore save and run a workflow that references a credential they have no access to, and have its decrypted value sent to a destination they choose.

## Patches

The issue has been fixed in n8n versions 1.123.85, 2.43.5, and 2.44.1. 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 credential ownership and remove any credentials from the instance that should not be accessible to member-level users.
- Monitor execution logs for unexpected credential usage by member accounts.

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_