N8n EUVD-2026-15943

Requires authenticated access to n8n workflow automation platform (versions before 2.14.1, 2.13.3, or 1.123.26) with global:member role. Attacker exploits name-based credential resolution and permission checker bypass to steal plaintext secrets from generic HTTP credentials (httpBasicAuth, httpHeaderAuth, httpQueryAuth) of other users on the same instance. No victim interaction needed.

The CVSS 4.0 score of 8.5 reflects high severity with network attack vector (AV:N), low complexity (AC:L), no attack requirements (AT:N), and low privileges required (PR:L). The vulnerability enables high impact to vulnerable system confidentiality (VC:H) and complete impact to subsequent systems (SC:H, SI:H, SA:H), indicating credential theft can cascade to other systems. However, real-world risk is moderated by several factors: exploitation requires authenticated access with member privileges, only affects Community Edition deployments, is limited to generic HTTP credential types (native integration credentials are protected), and patches are available for all affected versions. The attack is not automatable as it requires context-specific knowledge of credential names or IDs within the target instance. No EPSS score or KEV listing is provided in the intelligence data, and no public POC is mentioned in the GitHub advisory reference, suggesting limited active exploitation. For organizations using Community Edition with multiple users and generic HTTP credentials, this represents a genuine priority requiring prompt patching.

An authenticated attacker with member-level access to an n8n Community Edition instance identifies or enumerates credential names or IDs belonging to other users through the workflow interface. The attacker creates a workflow that references these generic HTTP credentials by name, exploiting the lack of ownership validation in the credential resolution path. When the workflow executes, the permissions checker skips validation for the generic HTTP credential type, allowing the attacker's workflow to decrypt and use the victim's plaintext credentials, which can then be exfiltrated through workflow outputs or used to access external systems.