Homepage

Protection Mechanism Failure Affecting n8n package, versions <2.23.2-r0

Severity

 Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.51% (40th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-MINIMOSLATEST-N8N-17134354
  • published3 Jun 2026
  • disclosed12 Jun 2026
Report a new vulnerability Found a mistake?

Introduced: 3 Jun 2026

NewCVE-2026-47209  (opens in a new tab)
CWE-693  (opens in a new tab)

How to fix?

Upgrade Minimos:latest n8n to version 2.23.2-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream n8n package and not the n8n package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

vm2 is an open source vm/sandbox for Node.js. Prior to version 3.11.4, the BaseHandler.set trap in bridge.js (line 1231) ignores the receiver parameter and unconditionally writes to the host target object. Per the Proxy set trap specification, when receiver !== proxy (e.g., when a child object inherits from the proxy via Object.create), the property assignment should create an own property on the receiver, not on the proxy target. The current implementation always calls otherReflectSet(object, key, value) against the host target, causing all inherited property writes to leak through to the host object. This bug provides an alternative attack vector for writing dangerous cross-realm Symbol keys (e.g., nodejs.util.promisify.custom) to host objects, bypassing any future per-trap isDangerousCrossRealmSymbol guard on the direct set path. This issue has been patched in version 3.11.4.