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


Severity

Recommended
0.0
high
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.45% (37th 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-20541766
  • published7 Oct 2026
  • disclosed17 Sept 2026

Introduced: 17 Sep 2026

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

How to fix?

Upgrade Minimos:latest n8n to version 2.41.3-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 before 3.11.8 does not fully enforce the allowAsync: false option in VM and NodeVM. While localPromise.prototype.then is replaced with a handler that throws 'Async not available', the sandbox's Promise static methods (Promise.resolve, Promise.all, Promise.race, Promise.any, and Promise.allSettled) still assimilate attacker-supplied thenables: native promise resolution performs PromiseResolveThenableJob and invokes the sandboxed code's then method in a microtask without passing through the patched then, so the async restriction is never applied. As a result, sandboxed script can schedule work that runs after VM.run() or NodeVM.run() has returned and outside the configured timeout, continuing to execute after the host believes execution is complete.

CVSS Base Scores

version 3.1