CVE-2026-42075: Evolver · Path Traversal via `--out` flag in `fetch` command allows Arbitrary File Write
Affects @evomap/evolverSource GCVE Database
Not known to be exploited · CVSS 8.1 High : upgrade to 1.69.3 soon.
Data as of 27 Oct 2026, 01:24 UTC
- Patch
- Available – fixed in 1.69.3
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 4 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade @evomap/evolver to 1.69.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npm@evomap/evolver | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available in version 1.69.3 of @evomap/evolver that fixes this vulnerability by presumably adding proper validation or sanitization of the --out flag input. Users should upgrade to version 1.69.3 or later to remediate this issue. Until patched, avoid using the --out flag with untrusted input or restrict its usage to safe directories.
Description
A path traversal vulnerability in the Evolver tool's fetch command allows attackers to write files to arbitrary filesystem locations via the --out flag. The flag accepts user input without validation, enabling directory traversal that can overwrite critical files or place malicious files in sensitive directories. This can lead to arbitrary file write, potentially enabling privilege escalation or persistent backdoors if exploited with sufficient permissions. The issue affects versions prior to 1.69.3 and has been fixed in version 1.69.3.