What is CVE-2026-86083?
n8n is an open source workflow automation platform. Prior to 1.123.76, 2.37.7, and 2.38.2, the legacy expression engine generated source text by calling the mutable global JSON.stringify while printing synthetic string literals and interpolating timezone data. An expression could replace JSON.stringify and cause later generated source to contain executable attacker-controlled code. The affected code-generation paths include packages/@n8n/expression-runtime/src/bridge/isolated-vm-bridge.ts and packages/@n8n/tournament/src/ExpressionBuilder.ts, and the issue does not affect the vm expression engine. This issue is fixed in versions 1.123.76, 2.37.7 and 2.38.2.
The record classifies CVE-2026-86083 under weakness class CWE-94. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 27 days ago.
Severity and exploitation probability
- CVSS v4.0 base score
- 7.7 — High (derived from score)
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N - EPSS (FIRST)
- 0.2% probability of exploitation in the next 30 days, higher than 20.0% of all scored CVEs
- CISA KEV
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Threadlinqs priority
- 4.7/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- Published
- 2026-09-08, last modified 2026-09-09
Is CVE-2026-86083 being exploited?
It currently carries a trending score of 35 in the Threadlinqs vulnerability feed.
Affected products and versions
- n8n-io: n8n
How to fix CVE-2026-86083
No vendor patch reference has been recorded for CVE-2026-86083 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.
Threat activity tracking CVE-2026-86083
No threat campaign in the Threadlinqs corpus currently references CVE-2026-86083, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.
Sources
Enriched from CVE.org, FIRST EPSS. Last verified by Threadlinqs on .