dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-42075

HIGH · 8.1 CVSS v3.1 Published 2026-05-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A path traversal vulnerability in Evolver's skill download (fetch) command allows arbitrary file writes. The --out= flag accepts user-controlled paths without validating for directory traversal sequences (e.g., ../), enabling attackers to write files outside the intended directory and potentially overwrite system files or place malicious content in sensitive locations.

MitigationUpgrade to version 1.69.3 or later. If immediate patching is not possible, implement path validation that sanitizes user-provided output paths by resolving canonical paths, rejecting paths containing traversal sequences, and restricting writes to an allowed base directory.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Evolver is installed
    Run 'evolver --version' or 'which evolver' to confirm the tool is present on the system
    Affected if If Evolver is not installed, this CVE does not apply to the environment
  2. Check installed Evolver version
    Execute 'evolver --version' and compare the output version number against 1.69.3 (any version prior to 1.69.3 is affected)
    Affected if If the installed version is lower than 1.69.3, the system is potentially affected by this path traversal vulnerability
  3. Confirm skill fetch command availability
    Run 'evolver skill fetch --help' or 'evolver skill --help' to verify the skill download functionality exists and includes the --out= flag
    Affected if If the skill fetch command with --out= flag is available and the version is below 1.69.3, the vulnerability is present
  4. Test path traversal susceptibility (optional)
    If authorized in a test environment, run 'evolver skill fetch <skill-name> --out=/tmp/../test' to see if directory traversal is blocked; in production, inspect any existing logs or configurations for suspicious --out= paths containing '../'
    Affected if If the command accepts path traversal sequences in the --out= parameter, the vulnerability is exploitable

The environment is affected if Evolver version is installed and is lower than 1.69.3, and the skill fetch/download command with the --out= flag is accessible to users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 1.69.3 or later. If immediate patching is not possible, implement path validation that sanitizes user-provided output paths by resolving canonical paths, rejecting paths containing traversal sequences, and restricting writes to an allowed base directory.

Recommended fix High confidence

1.69.3

  1. Upgrade Evolver to version 1.69.3 or later using your package manager or dependency management tool (e.g., pip install evolver==1.69.3, npm update evolver, or equivalent)
  2. Verify the upgrade was successful by checking the installed version (e.g., evolver --version)
  3. Test the skill download (fetch) command with the --out= flag to confirm the path traversal vulnerability is mitigated - ensure paths are validated and traversal attempts are rejected

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-42075 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-42075 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data