CVE-2026-21858: Ni8mare
- Vendor
- N8n
Ni8mare is an unauthenticated file-access vulnerability in n8n versions 1.65.0 through versions preceding 1.121.0. Content-Type confusion in webhook and form request handling allows crafted JSON requests to supply attacker-controlled file metadata instead of metadata generated by the multipart upload parser. The parseBody() processing path permits attacker-supplied file paths to populate internal request data, which certain form-based workflows subsequently trust when reading files. Exploitation can expose sensitive server files and, depending on deployment configuration and workflow capabilities, enable authentication forgery and remote code execution.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Attackers can disclose server files readable by the n8n process, potentially exposing application databases, credentials, authentication secrets, and other sensitive information. Where accessible secrets permit administrator-session forgery, attackers may take over the n8n instance, access connected-service credentials, modify workflows, and execute operating-system commands through available workflow capabilities. Full host compromise depends on deployment privileges and isolation; arbitrary file access is the direct vulnerability outcome.
Mitigation
If you can’t patch tonight, do this now.
No official workaround is available. Until upgrading, restrict or disable publicly accessible webhook and form endpoints, require authentication for exposed Forms and Webhooks, and limit network access to trusted clients. Monitor for unexpected JSON submissions containing file-path metadata to form or webhook endpoints; request filtering can provide supplementary protection but does not replace patching.
Remediation
Patch, then assume compromise.
Upgrade n8n to version 1.121.0 or later, which fixes CVE-2026-21858. Use a current supported release to address additional vulnerabilities that could participate in exploitation chains.
Exploits
13 exploits validated by Mallory's analysis. Hidden: 14 rejected by Mallory's analysis as not a working exploit; 1 not yet analyzed, such as Exploit-DB entries.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2026-21858 exploited in the wild?
- Yes. As of Oct 26, 2026, Mallory has reports of exploitation in the wild.
- Is there a public exploit for CVE-2026-21858?
- Yes. Mallory tracks 13 public exploits or proofs of concept for CVE-2026-21858, the earliest disclosed Oct 12, 2023.
- Is there a patch for CVE-2026-21858?
- Upgrade n8n to version 1.121.0 or later, which fixes CVE-2026-21858. Use a current supported release to address additional vulnerabilities that could participate in exploitation chains.
- What products are affected by CVE-2026-21858?
- N8n.
- How severe is CVE-2026-21858?
- CVE-2026-21858 has a CVSS v3.1 score of 10.0 (Critical) and an EPSS score of 78.2% (100th percentile) as of Oct 26, 2026.
Recent activity
224 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.