CVE-2026-59254 n8n CVE debrief

Who should care

Defenders responsible for n8n deployments, particularly those with sensitive data, should assess exposure and prioritize remediation. This includes reviewing current n8n versions, identifying potential vulnerabilities, and implementing necessary upgrades or mitigations. Additionally, defenders should restrict node expression access to sensitive data and monitor for suspicious node expression usage to prevent unauthorized access to sensitive information.

Why it matters

CVE-2026-59254 is a medium-severity information disclosure vulnerability in n8n before version 2.28.1, allowing authenticated project editors to access plaintext external secret values. Defenders should prioritize verification, remediation, and restricted access to sensitive data.

• Potential unauthorized access to sensitive data
• Need to verify and upgrade to n8n version 2.28.1 or later
• Require restricted node expression access to sensitive data

Technical summary

The vulnerability allows authenticated project editors to read plaintext external secret values by referencing them in node expressions without requiring explicit secrets access permissions in n8n before version 2.28.1. This occurs because n8n does not properly restrict access to external secrets in node expressions, leading to potential unauthorized access to sensitive information. Defenders should prioritize verifying and upgrading to n8n version 2.28.1 or later, and restrict node expression access to sensitive data.

Defensive priority

Defenders should prioritize verifying and upgrading to n8n version 2.28.1 or later, and restrict node expression access to sensitive data.

Recommended defensive actions

• Verify and upgrade to n8n version 2.28.1 or later
• Restrict node expression access to sensitive data
• Monitor for suspicious node expression usage
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, but do not specify which versions are affected or fixed beyond n8n 2.28.1. Vendor remediation and compensating controls require verification.

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.