CVE-2026-77071 n8n-io CVE debrief

Who should care

Organizations using n8n for workflow automation should be aware of this vulnerability and take steps to patch or mitigate it. Affected operators, platforms, and security teams should review the official advisory and CVE record to validate affected scope, severity, and vendor guidance. They should also plan vendor-supported updates or mitigations through normal change control where exposure is confirmed and review compensating controls for exposed systems while remediation is scheduled and verified. Additionally, they should check relevant monitoring, detection, and logs for exposed assets that need extra review and track exceptions, retest remediated assets, and close the item only after evidence is documented. The vulnerability has a CVSS score of 7.1 and a HIGH severity rating, indicating a significant risk to affected systems. Therefore, it is essential for organizations to prioritize patching to prevent potential full-table disclosure, deletion, or modification. This may involve reviewing and updating existing security policies, procedures, and incident response plans to ensure they are effective in addressing this type of vulnerability. Furthermore, organizations should consider implementing additional security controls, such as monitoring and detection systems, to help identify and respond to potential attacks. By taking these steps, organizations can help protect their systems and data from the potential impacts of this vulnerability. Finally, organizations should also consider conducting regular security audits and risk assessments to identify and address potential vulnerabilities before they can be exploited. This can help reduce the likelihood of a successful attack and minimize the potential impacts of a breach. Overall, it is essential for organizations to take a proactive and multi-faceted approach to addressing this vulnerability and protecting their systems and data. This may involve a significant amount of time and resources, but it is essential for ensuring the security and integrity of affected systems. The vulnerability highlights the importance of secure coding practices, thorough testing, and robust security controls in preventing and mitig

Technical summary

The n8n workflow automation tool contains a PostgREST filter injection vulnerability in its Supabase node. The vulnerability occurs when building filter queries by concatenating an expression-bindable value without escaping, allowing attackers to inject conditions that widen the filter to match every row. This could lead to full-table disclosure, deletion, or modification. The vulnerability affects n8n versions before 1.123.69, 2.33.4, and 2.34.1.

Defensive priority

Organizations using n8n should prioritize patching to prevent potential full-table disclosure, deletion, or modification.

Recommended defensive actions

• Apply patches to n8n versions before 1.123.69, 2.33.4, and 2.34.1
• Implement compensating controls to restrict access to sensitive data
• Monitor for suspicious activity on affected systems
• Review the official advisory and 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
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE-2026-77071 record indicates a PostgREST filter injection vulnerability in n8n's Supabase node, allowing attackers to inject conditions that widen filters to match every row. Evidence is based on official CVE and NVD records, as well as vendor advisories. The vulnerability affects n8n versions before 1.123.69, 2.33.4, and 2.34.1. Defenders should verify affected product deployments, review official advisories, and plan vendor-supported updates or mitigations.

Official resources