n8n EUVD-2026-112374

Requires an authenticated n8n user who holds view access to a workflow's executions but is NOT authorized to read the underlying credential (PR:L). Exploitation further requires that a credentialed operation in one of the specific affected nodes - Git, MongoDB Atlas Vector Store, or Google Cloud Storage - has actually FAILED, which is what causes the secret (Git password/token, MongoDB database password, or Google access token) to be written into the stored execution error data (this is the AT:P attack requirement). Limiting factors: the attacker must already have an account and execution-read permission on the affected instance; the workflow must use one of these three node types with a credential; and a failing operation must have occurred. It does not apply to successful executions or to users without execution-read access.

This is a moderate, access-gated information-disclosure flaw (CWE-209) rather than a high-urgency issue. The CVSS 4.0 vector (AV:N/AC:L/AT:P/PR:L/UI:N, VC:L, with subsequent-system SC:H/SI:H) scores 5.3 (Medium): exploitation is network-reachable and low-complexity, but requires existing low-privilege access (PR:L) and carries an attack requirement (AT:P) because a credentialed operation must actually fail to populate the error data. The vuln.today decision label is 'this_month' (not act_now/emergency), and the vulnerability is NOT on CISA KEV and has no EPSS score supplied, so there is no signal of active or widespread exploitation. No exploit or PoC code reference is present in the input - only vendor/coordinator advisories (GHSA and VulnCheck) - so this is no public exploit identified at time of analysis. The signals are internally consistent: a confirmed-but-not-exploited credential-leak to under-privileged insiders. Real priority is driven by insider/least-privilege exposure in multi-tenant n8n deployments, not by remote mass exploitation.

In a shared n8n instance, a low-privileged user is granted permission to view a workflow's execution history but is deliberately not given access to its stored credentials. A Git, MongoDB Atlas Vector Store, or Google Cloud Storage operation in that workflow fails, and n8n writes the error - which embeds the credential secret - into the execution data. The user opens the failed execution and reads the Git password/token, MongoDB database password, or Google access token directly. No PoC or exploit code is referenced in the available sources.