PatchSiren cyber security CVE debrief
CVE-2026-72749 n8n-io CVE debrief
The n8n workflow automation tool contains a prototype pollution vulnerability in the Edit Fields (Set) node, which allows an authenticated user to corrupt a shared global in the main Node.js process. This corruption causes the instance to fail every authenticated request, resulting in an instance-wide denial of service for all users until the process is restarted. The vulnerability affects n8n versions before 1.123.67, 2.31.5, and 2.32.1. Users with access to the n8n instance, administrators, and security teams should be aware of this vulnerability and take immediate action to patch or mitigate it. Evidence is based on official CVE and NVD records, as well as advisories from the vendor and Vulncheck. To address this vulnerability, it is essential to patch n8n to a secure version and restrict access to the Edit Fields (Set) node to trusted users only.
- Vendor
- n8n-io
- Product
- n8n
- CVSS
- HIGH 7.1
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-11
- Original CVE updated
- 2026-08-31
- Advisory published
- 2026-08-11
- Advisory updated
- 2026-08-31
Who should care
Users of n8n versions before 1.123.67, 2.31.5, and 2.32.1 should be aware of this vulnerability and take immediate action to patch or mitigate it. This includes administrators and users with access to the n8n instance, as well as security teams responsible for monitoring and protecting the environment.
Technical summary
The n8n workflow automation tool contains a prototype pollution vulnerability in the Edit Fields (Set) node. An authenticated user can exploit this vulnerability by naming a field after an inherited built-in method path, corrupting a shared global in the main Node.js process. This corruption causes the instance to fail every authenticated request, resulting in an instance-wide denial of service for all users until the process is restarted.
Defensive priority
Authenticated users with low privileges can exploit this vulnerability to cause an instance-wide denial of service, making immediate patching a high priority.
Recommended defensive actions
- Patch n8n to version 1.123.67, 2.31.5, or 2.32.1, or later
- Restrict access to the Edit Fields (Set) node to trusted users only
- Monitor for suspicious activity on the n8n instance
- Consider implementing additional security controls, such as Web Application Firewalls (WAFs) or intrusion detection systems
- 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
Evidence notes
The CVE-2026-72749 record indicates a high-severity vulnerability in n8n versions before 1.123.67, 2.31.5, and 2.32.1. The vulnerability is due to prototype pollution in the Edit Fields (Set) node, which allows an authenticated user to corrupt a shared global in the main Node.js process, leading to an instance-wide denial of service. Evidence is based on official CVE and NVD records, as well as advisories from the vendor and Vulncheck.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-72749 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-72749
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-72749 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-72749
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/n8n-io/n8n/security/advisories/GHSA-xwx6-jjhv-84p8
-
Source reference
Unverified legacy reference
URL: https://www.vulncheck.com/advisories/n8n-before-prototype-pollution-via-edit-fields
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.