iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
The likely “second round” behind this headline is n8n’s February 25, 2026 disclosure of an expression-sandbox escape that can lead to remote code execution. It is an urgent patching issue for self-hosted environments: an authenticated account that can create or modify workflows may be able to make the n8n host execute unintended system commands.
What the “second round” most likely means
The headline does not identify a CVE or date. The closest primary-source match is n8n’s maintained GitHub Security Advisory, Expression Sandbox Escape Leading to RCE (GHSA-vpcf-gvg4-6qwr), published February 25, 2026. n8n described it as an additional expression-evaluation exploit found and fixed after CVE-2025-68613. Calling it the “second round” is therefore an evidence-based interpretation, not an official incident label.
This February issue should not be merged with a separate January form-workflow disclosure or with later September advisories. They have different prerequisites, affected versions and fixes.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Why the February flaw creates corporate risk
The required access is authenticated workflow editing
According to n8n, “An authenticated user with permission to create or modify workflows could abuse crafted expressions in workflow parameters to trigger unintended system command execution on the host running n8n.” This is not an unauthenticated RCE in the February advisory. The attacker needs a valid account and workflow creation or modification permission.
#1 Best Overall
- Compact and Efficient Design: The FortiGate 40F is designed for small to mid-sized businesses and enterprise branch offices, featuring a compact, fanless desktop form factor that ensures quiet operation and minimizes space usage.
- Robust Connectivity Options: Equipped with 5 GE RJ45 ports, including 1 WAN port and 4 internal ports, this model provides essential connectivity and flexibility for various network configurations in a small-scale environment.
- High-Performance Security: Offers up to 1 Gbps IPS throughput and 600 Mbps threat protection throughput, using Fortinet’s purpose-built security processor technology to deliver industry-leading performance and protection for SSL encrypted traffic.
- Advanced Threat Protection: Integrated with Fortinet’s AI-powered FortiGuard Labs, the FortiGate 40F offers comprehensive cybersecurity, identifying and mitigating both known and unknown threats to maintain robust security across your network.
- Simplified Management and Deployment: Features a user-friendly management console that provides comprehensive network automation and visibility, coupled with Zero Touch Integration with Fortinet’s Security Fabric for easy deployment.
Impact depends on the n8n host
Successful command execution would occur with the operating-system privileges available to the n8n process. A highly privileged service account, broad network egress, mounted secrets or access to internal services can turn a workflow-editor compromise into a wider corporate incident. A tightly restricted account and segmented host reduce blast radius, but they do not remove the vulnerability.
Severity and evidence limits
n8n rates GHSA-vpcf-gvg4-6qwr as Critical and assigns a CVSS v4 base score of 9.4. That is the maintainer’s severity assessment. The advisory reviewed for this article does not establish confirmed exploitation in the wild, name a victim or quantify corporate losses.
Am I running an affected n8n version?
Compare the exact semantic version and release branch of every instance with the February advisory. The affected ranges and the patched releases named by n8n are:
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallRank #2
- HARDWARE PLUS SECURITY SERVICES: FortiGate-60F Firewall Appliance bundled with 1 year of FortiCare Premium and FortiGuard Unified Threat Protection.
- UNIFIED THREAT PROTECTION (UTP): Secures against advanced online threats with comprehensive web filtering and anti-botnet technologies.
- OPTIMIZED FOR MEDIUM-SIZED BUSINESSES: Tailored for businesses needing robust security without the infrastructure of larger enterprises.
- RELIABLE CUSTOMER SUPPORT: FortiCare Premium ensures high-quality support and service continuity.
- EFFECTIVE PROTECTION: Employs advanced filtering technologies to safeguard against sophisticated threats.
| Release line | Affected versions | Patched version named by n8n |
|---|---|---|
| 1.x | Earlier than 1.123.22 | 1.123.22 |
| 2.x | 2.0.0 through versions earlier than 2.9.3 | 2.9.3 |
| 2.x | 2.10.0 | 2.10.1 |
These are historical thresholds from the February 25 advisory. Before deploying, check n8n’s current release guidance and support status for your branch; a later supported release may be preferable to installing the minimum fixed version.
Build a complete inventory
- List every self-hosted n8n production, staging and development instance, including separate workers and queue-mode components.
- Record the exact version shown by each instance, such as the About/help information or startup log. For containers, record both the image tag and immutable image digest where available.
- Identify the release branch and whether workflow editors can create or modify workflows.
- Compare each record with the three February ranges above. Treat an unknown version as unverified until you can establish it.
What administrators should do now
- Upgrade affected instances. Move to the applicable patched release or a later supported release, following current n8n upgrade instructions. Test representative workflows in a staging environment, then update production and all workers consistently.
- Review workflow-editor permissions. Remove workflow creation and editing rights from accounts that do not need them. Separate trusted builders from users who only execute approved workflows.
- Reduce host privileges. Run n8n under a dedicated operating-system account, remove unnecessary administrative rights and review filesystem permissions, mounted volumes, credentials and environment variables.
- Restrict network reachability. Limit inbound access to the editor and webhook endpoints, segment the n8n host and constrain outbound connections to the services workflows genuinely require.
- Investigate before and after upgrading. Review authentication events, workflow changes, expression-heavy workflows, process launches and unusual outbound traffic. Preserve relevant logs according to your incident-response policy.
- Rotate exposed secrets when warranted. If investigation shows that a host or workflow may have been abused, rotate API keys, database credentials, cloud tokens and other secrets accessible to the n8n process.
What if you cannot patch immediately?
n8n recommends restricting workflow creation and editing to fully trusted users and hardening operating-system privileges and network access as interim measures. The advisory explicitly warns: “These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.”
- Disable or remove nonessential editor accounts and enforce strong authentication through your identity provider.
- Pause unapproved workflow changes and require a security-reviewed change process.
- Run the service with the least privilege possible and remove broad host mounts and unnecessary environment secrets.
- Apply egress controls and block access from the n8n host to systems that workflows do not need.
- Set a dated upgrade deadline; do not treat access restrictions as a permanent fix.
Self-hosted and cloud deployments are not equivalent
The February advisory’s version ranges are most directly actionable for self-hosted operators, who control the upgrade. Do not assume that a general statement about automatic cloud patching proves that every cloud tenant is already protected from every later advisory. Confirm the status of your n8n Cloud workspace with the provider or its service notices, and still review which users can edit workflows.
Rank #3
- 【Up to 1100 Mbps VPN Speed 】 Hardware-accelerated WireGuard and OpenVPN-DCO deliver up to 1100 Mbps VPN throughput, over 3× faster than Brume 2 for smooth remote access and file transfers.
- 【Three 2.5G Ports & Multi-WAN】Tri-port 2.5GbE design with flexible WAN LAN configuration supports multi-gigabit wired setups, dual-ISP Multi-WAN and failover to keep home and SOHO networks online.
- 【Stealth VPN Obfuscation】VPN obfuscation disguises VPN traffic as regular HTTPS, helping you evade blocking, bypass restrictive networks and maintain stable, private connections.
- 【DPI protection】Deep Packet Inspection with visual dashboards blocks adult/gambling/malicious sites, while SQM and QoS prioritize gaming, calls, and video when bandwidth is tight
- 【OpenWrt & USB 3.0 Expansion】OpenWrt with 1GB DDR4 and 8GB eMMC lets you install plugins and build VPN, ad-blocking or NAS, while USB 3.0 Type‑C connects high-speed storage or 4G/5G dongles
Do not confuse this with the January form-workflow vulnerability
On January 8, 2026, n8n described a different critical issue affecting self-hosted versions 1.65 through 1.120.4 only when an active workflow used both a Form Submission trigger and a Form Ending node that returned a binary file. Under limited conditions, an unauthenticated person who could reach the form could obtain underlying filesystem reads.
Free tools Windows power users keep installed
One-click scans. No signup required.
n8n said version 1.121.0 fixed that issue, that 2.x versions already contained the fix and that cloud instances had been upgraded automatically. Those conditions and fixes do not replace the February expression-sandbox thresholds.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How the September 2026 advisories fit the timeline
n8n continued publishing separate security updates in September. Its September 2 update listed fixes for the issues it covered in version 1.123.76, beta 2.38.2 and stable 2.37.7, and said cloud versions were patched automatically. The Canadian Centre for Cyber Security’s September 11 notice listed the same branch thresholds for the issues it covered.
Rank #4
- Runs UniFi Network for full-stack network management
- Manages 30+ UniFi Network devices and 300+ clients
- 1 Gbps routing with IDS/IPS
- Multi-WAN load balancing
- 0.96" LCM status display
Those September numbers are not substitutes for the February advisory’s 1.123.22, 2.9.3 and 2.10.1 thresholds. The repository index also showed September 16 advisories involving credential, injection and authorization problems. They demonstrate ongoing disclosure activity, not one continuous February RCE campaign.
What security claims n8n makes about its program
On its security page, n8n says it conducts third-party vulnerability scans of its production environment at least every 90 days and third-party penetration tests at least once a year. These are vendor-described program practices; they are not an independent audit of the February patch or proof that a particular deployment is safe.
Recommended Free Tools
Corporate risk decision checklist
- Patch status: every instance is at or above the applicable fixed release, or has an approved, time-limited exception.
- Editor exposure: only identified, authenticated and trusted users can create or modify workflows.
- Host containment: the n8n process lacks unnecessary administrative rights, sensitive mounts and broad credentials.
- Network containment: inbound editor access and outbound connections are limited and monitored.
- Detection: logs cover account use, workflow edits, process creation and unusual network activity.
- Incident readiness: credential rotation and evidence-preservation steps are documented if suspicious activity appears.
Bottom line
Treat the February 25, 2026 expression-sandbox escape as a critical patching task, not as proof that n8n has suffered a confirmed corporate breach. Determine your exact branch, apply the corresponding fixed release or a later supported version, restrict workflow editing while you patch and contain the n8n host. Keep the January form-file disclosure and September advisories on separate tracking records so that each issue is assessed against its own conditions and thresholds.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
