Quick answers
- Is CVE-2026-85165 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-85165 being exploited in the wild.
- How severe is CVE-2026-85165?
- Critical severity, with a CVSS score of 9.9, published 3 September 2026.
- Which products and versions are affected?
- N8n < 2.36.2, < 2.35.4.
- Is there a fix for CVE-2026-85165?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-85165 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-85165?
- Check whether you run N8n at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
This vulnerability exists in n8n's expression sandbox, which fails to properly rewrite free identifiers appearing in spread, computed-key, switch-case, and class-extension positions. Consequently, these identifiers resolve against process globals instead of being sandboxed, exposing over thirty host globals. An authenticated attacker with workflow-edit permission can craft malicious expressions that mutate these shared objects through expression evaluation. The changes persist process-wide across all subsequent expression evaluations until the n8n process is restarted. The vulnerability is classified as eval injection (CWE-95) and requires only low privilege (workflow-edit) and no user interaction, making it exploitable via network access.
Affected products
- n8n n8n < 2.36.2, < 2.35.4
Timeline
- 2026-08-19: disclosed: GitHub Security Advisory GHSA-fg85-4wv2-p98j published
- 2026-09-03: advisory: CVE-2026-85165 published on NVD