Task 1: Introduction: When Automation Escapes the Sandbox
Priya Raman is head of the Automation team at Copperline Energy (a regional energy operator). Their self-hosted n8n instance is the operational plumbing, in that it's what handles the meter data syncs, the enrichment of outage tickets, the scheduled reporting, etc. The estate is on an older n8n release behind very slow change control, so security releases are effectively on hold. She's had to commission an internal self-audit because no one knows what that pin actually costs.
CVE-2026-119408 is n8n's October 2026 entry in the Common Vulnerabilities and Exposures (CVE) catalog, the public registry where disclosed flaws receive stable identifiers. It is mirrored in the Open Source Vulnerabilities (OSV) record. n8n deprecated certain workflow nodes, marking them as replaced and slated for removal. Those same nodes kept executing user JavaScript in the n8n main process, outside the isolated task runner that ordinary workflow code runs in. GitHub's advisory GHSA-9p7v-45m2-wxgj, titled Deprecated Code Nodes Allow Code Execution in the n8n Main Process, records the defect.
The CVE Numbering Authority record at VulnCheck carries the score: the Common Vulnerability Scoring System (CVSS), version 4.0, grades the flaw 8.7 out of ten, High. It also assigns the weakness to CWE-653 (Improper Isolation or Compartmentalization), which names the missing isolation exactly. The score is a number for the question Priya's audit is asking. The same record compresses all of that into one vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N. The letters read as noise now; they won't once the lab has shown you what each input describes.
The lab is, in effect, Priya's estate. One target VM has all three services.
| Service | Hostname | Port |
|---|---|---|
| Production n8n, the vulnerable target | automation.copperline.thm |
5678 |
| Staging n8n, the patched control | automation-staging.copperline.thm |
5679 |
| Team snippet store | automation-files.copperline.thm |
8080 |
Production is still on 2.42.5. Staging is running 2.42.6 (the first patched release on that line). The snippet store serves up the team's exported workflow files via plain HTTP. The three names all point to the same address (MACHINE_IP), which TryHackMe assigns when the machine starts. They're all wired together via a single /etc/hosts entry, which is added once the machine is up.
You have a member seat on default settings, import one of the team's own workflow snippets and watch the code run from a node that shouldn't even be there. The same workflow then ends up on the patched staging twin and is refused at save time there. The audit from that point on is defensive, and you'll work out how that exposure is detected and closed.
The sandbox escape follows 0x4bd0's published write-up and the HTTP request flow follows the lab Abraxas Labs released alongside their disclosure, both credited where the room uses them.
Learning Objectives
This room covers one n8n vulnerability from record to working escape to verified patch. You'll in particular learn how to:
- Explain the deprecated-node isolation gap and its CVE record.
- Establish a workflow-creating foothold on default settings.
- Import and run a workflow that names a hidden node type
- Trace the sandbox escape to the real environment.
- Recover environment secrets through the credited escape.
- Drive the identical workflow at the patched control.
- Plan detection and mitigation for the exposure
Room Prerequisites
You should be comfortable driving a web app from the browser and reading a request in the dev tools network tab. Basic Linux shell work and curl against an HTTP API completes the picture. No n8n experience is required, as the room teaches you every n8n concept it uses as it comes up. If you're new to the series, then the earlier rooms in the Recent Threats module cover similar ground and would make a good warm-up, though again you don't need them for this room.
Before you start Task 2, press the Start AttackBox button to start the Attacker machine and press the Start Machine button to start the Target machine so that they are ready when you need them in later tasks.