{"answers":{"affected":"2 open source packages ship an affected version, including @evomap/evolver.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-42075 exists.","fix":"Upgrade @evomap/evolver to 1.69.3 or later.","what":"CVE-2026-42075 is a high-severity path traversal vulnerability in EvoMap evolver, published on 4 May 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-42075 and fix it if it is affected.\n\nWhat it is: CVE-2026-42075 is a high-severity path traversal vulnerability in EvoMap evolver, published on 4 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-42075 exists.\n\nAffected packages and fixed versions:\n- @evomap/evolver (npm): affected all versions; fixed in 1.69.3\n- @evomap/evolver (npm): affected all versions; fixed in 1.69.3\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-42075/ (Markdown: https://insights.sbomify.com/CVE-2026-42075/index.md)","id":"CVE-2026-42075","markdown":"https://insights.sbomify.com/CVE-2026-42075/index.md","name":"CVE-2026-42075","record":{"aliases":["GHSA-r466-rxw4-3j9j"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"AI agent engine","requires_auth":"low_privilege","summary":"Attackers can write arbitrary files to the filesystem via the fetch command's output flag, potentially overwriting critical system files.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Evolver is a GEP-powered self-evolving engine for AI agents. Prior to version 1.69.3, a 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 location. This issue has been patched in version 1.69.3.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Evolver: Path Traversal via `--out` flag in `fetch` command allows Arbitrary File Write","id":"CVE-2026-42075","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"Evolver: Command Injection via `execSync` in `_extractLLM()` function allows Remote Code Execution","id":"CVE-2026-42076"},"packages":[{"ecosystem":"npm","fixed":["1.69.3"],"introduced":["0"],"last_affected":[],"package":"@evomap/evolver","purl":null,"source":"GHSA-r466-rxw4-3j9j"},{"ecosystem":"npm","fixed":["1.69.3"],"introduced":["0"],"last_affected":[],"package":"@evomap/evolver","purl":"pkg:npm/%40evomap/evolver","source":"GHSA-r466-rxw4-3j9j"}],"prev":{"headline":"OpenClaude: Sandbox Bypass via Model-Controlled `dangerouslyDisableSandbox` Input","id":"CVE-2026-42074"},"products":["evolver"],"published":"2026-05-04","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-04","vendors":["EvoMap"]},"summary":"Attackers can write arbitrary files to the filesystem via the fetch command's output flag, potentially overwriting critical system files.","url":"https://insights.sbomify.com/CVE-2026-42075/"}