Is This vulnerability exploited in the wild?

No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.

How severe is This vulnerability?

Low severity, with a CVSS score of 3.1, published 5 May 2026.

Which products and versions are affected?

EvoMap Evolver <= 1.70.0-beta.4; @evomap/evolver (npm) SEMVER:introduced=0,fixed=1.70.0-beta.5.

Is there a fix for This vulnerability?

Yes. @evomap/evolver (npm): upgrade to 1.70.0-beta.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is This vulnerability attacked?

It is attacked over the network, in a software library.

Check whether you run EvoMap Evolver or @evomap/evolver (npm) 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.

EvoMap evolver validator sandbox RCE via npm/npx lifecycle scripts

Q: Which products and versions are affected?

EvoMap Evolver <= 1.70.0-beta.4; @evomap/evolver (npm) SEMVER:introduced=0,fixed=1.70.0-beta.5.

Q: Is there a fix for This vulnerability?

Yes. @evomap/evolver (npm): upgrade to 1.70.0-beta.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is This vulnerability attacked?

It is attacked over the network, in a software library.

Q: Am I affected?

Check whether you run EvoMap Evolver or @evomap/evolver (npm) 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.

Severity: low · CVSS 3.1 · Published 2026-05-05

@evomap/evolver is a package validation tool that runs untrusted validation tasks in a sandbox. The sandbox incorrectly allows npm and npx commands, which by design execute arbitrary code via package lifecycle scripts (preinstall, install, postinstall). An attacker controlling or intercepting the Hub service can deliver malicious validation tasks that achieve remote code execution on every validator node within 60 seconds of the next daemon poll, with no authentication or user interaction required.

Technologies: EvoMap Evolver, @evomap/evolver (npm). Vendors: EvoMap, npm.

Quick answers

Is This vulnerability exploited in the wild?: No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
How severe is This vulnerability?: Low severity, with a CVSS score of 3.1, published 5 May 2026.
Which products and versions are affected?: EvoMap Evolver <= 1.70.0-beta.4; @evomap/evolver (npm) SEMVER:introduced=0,fixed=1.70.0-beta.5.
Is there a fix for This vulnerability?: Yes. @evomap/evolver (npm): upgrade to 1.70.0-beta.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is This vulnerability attacked?: It is attacked over the network, in a software library.
Am I affected?: Check whether you run EvoMap Evolver or @evomap/evolver (npm) 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.

How to fix

@evomap/evolver (npm): upgrade to 1.70.0-beta.5 or later
```
npm install @evomap/evolver@1.70.0-beta.5
```

Technical details

The vulnerability is a sandbox escape caused by whitelisting npm and npx in the hard executable allowlist, combined with a missing signature verification on Hub responses. The validator's fetchValidationTasks() signs the outbound request but does not verify the Hub's JSON response before parsing validation_commands. Those commands are passed directly to runInSandbox() without policyCheck validation. The parseCommand() parser only blocks shell metacharacters, allowing benign-looking npm install commands to reach spawn(). npm's documented behavior executes preinstall/install/postinstall lifecycle scripts and npx downloads and executes remote package binaries—both bypass the intended threat model of allowlist-based command filtering. The nominal sandbox (fresh cwd, stripped env, but no container/chroot/seccomp/UID drop) cannot contain this code execution. Patches are available in v1.70.0-beta.5 and later. Attack vector is network; validator mode is enabled by default since v1.69.0.

Affected products

EvoMap evolver <= 1.70.0-beta.4

Timeline

2026-05-05: disclosed
2026-05-05: patched: Fixed in v1.70.0-beta.5

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.