CVE-2026-72774 n8n-io CVE debrief

Who should care

Defenders responsible for n8n deployments, particularly those with shared workflows and sensitive credentials, should assess exposure and prioritize remediation. This includes reviewing and restricting access to sensitive workflows and credentials, as well as verifying and upgrading to a fixed version of n8n. Additionally, defenders should monitor for suspicious activity in n8n workflows and review compensating controls for exposed systems while  

Why it matters

CVE-2026-72774 is a high-severity vulnerability in n8n that allows authenticated users to bypass credential authorization checks, potentially leading to unauthorized access to sensitive credentials. Defenders responsible for n8n deployments should assess exposure and prioritize remediation.

• Potential unauthorized access to sensitive credentials
• Possible exfiltration of credentials by authenticated users
• Bypass of credential authorization checks in n8n workflows
• Verification of affected versions and exposure required

Technical summary

The vulnerability exists in the HTTP Request node of n8n, allowing an authenticated user with edit access to a shared workflow to reference another user's credential while specifying the credential type via an expression. This bypasses the pre-execution permission check, enabling the loading of the credential at execution time. The vulnerability has a CVSS score of 7.1 and is considered high-severity. Affected versions of n8n include those prior to 1.123.67, 2.31.5, and 2.32.1. Exploitation requires knowing the target credential's identifier.

Defensive priority

Defenders should prioritize verifying and upgrading to a fixed version of n8n, as well as reviewing and restricting access to sensitive workflows and credentials.

Recommended defensive actions

• Verify and upgrade to a fixed version of n8n (1.123.67, 2.31.5, or 2.32.1)
• Review and restrict access to sensitive workflows and credentials
• Monitor for suspicious activity in n8n workflows
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its CVSS score of 7.1 and affected versions of n8n. Vendor advisories and third-party reports offer additional context and mitigation guidance.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.