n8n before 2.36.2 Credential Exfiltration via Workflow Tool Node
Impact
n8n versions before 2.35.4 and 2.36.x before 2.36.2 are affected by credential exfiltration via workflow tool nodes. An attacker with access to create or update workflows can persist a node referencing a credential they do not own. This can lead to credential exfiltration when the workflow is executed under an identity that holds the credential.
Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.Affected packages
Affected products
Vendor version evidence. Product records are separate from automatic dependency matching.
n8n-io · VulnCheck
n8n
2 ranges
n8n-io · VulnCheck
n8n
Package identity
pkg:npm/n8nExplore n8n →Identity supplied by VulnCheck. Version matching requires compatible range evidence.
Compare with this publisher’s ranges. This does not inspect your installation.
affected
2.36.0 → before 2.36.2
semver versions
unaffected
2.36.2
semver versions
Other versions: unaffected
n8n-io · VulnCheck
n8n
2 ranges
n8n-io · VulnCheck
n8n
Package identity
pkg:npm/n8nExplore n8n →Identity supplied by VulnCheck. Version matching requires compatible range evidence.
Compare with this publisher’s ranges. This does not inspect your installation.
affected
0 → before 2.35.4
semver versions
unaffected
2.35.4
semver versions
Other versions: unaffected
Original source description
n8n before 2.35.4 and 2.36.x before 2.36.2 does not validate credential references in the inline workflow JSON of nodes that execute an inline sub-workflow (e.g., the Workflow Tool node). A shared-workflow editor, or any user creating/updating a workflow via the REST API, Public API, or MCP, can persist a node referencing a credential they do not own. When the workflow is later executed under an identity that holds the credential, the inline sub-workflow resolves the secret and can send it to an attacker-controlled endpoint, resulting in credential exfiltration.
Inside the record
Evidence available
Describes the evidence in this view, not whether the product is safe.
Original records
CVE-2026-85166View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.
cve.new JSON →Underlying weaknesses
The source’s classification of what caused the vulnerability.
Environment requirements
These conditions apply together as specified by the publisher. A matching product name alone does not establish exposure.
VulnCheck · platform conditions
Any condition may hold
Vulnerable product
cpe:2.3:a:n8n:n8n:*:*:*:*:*:*:*:*From (inclusive): 2.36.0
Before: 2.36.2
Any condition may hold
Vulnerable product
cpe:2.3:a:n8n:n8n:*:*:*:*:*:*:*:*Before: 2.35.4
Original applicability statements
[
{
"nodes": [
{
"operator": "OR",
"negate": false,
"cpeMatch": [
{
"vulnerable": true,
"criteria": "cpe:2.3:a:n8n:n8n:*:*:*:*:*:*:*:*",
"versionEndExcluding": "2.36.2",
"versionStartIncluding": "2.36.0"
}
]
}
]
},
{
"nodes": [
{
"operator": "OR",
"negate": false,
"cpeMatch": [
{
"vulnerable": true,
"criteria": "cpe:2.3:a:n8n:n8n:*:*:*:*:*:*:*:*",
"versionEndExcluding": "2.35.4"
}
]
}
]
}
]Contributing organizations · 2
Assigning organization
Additional data publisher
What changed
Follow changesLarge field values are marked as truncated previews. Original source snapshots remain retained.