# CVE-2026-58171: Vibe-Trading < 0.1.10 - Path Traversal via Swarm Run Identifier

> Attackers can read or overwrite arbitrary JSON files via crafted run identifiers in Vibe-Trading swarm tools.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jun 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-mjrq-xg2m-qg94

## What is CVE-2026-58171?

CVE-2026-58171 is a low-severity path traversal vulnerability in HKUDS Vibe-Trading, published on 30 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Vibe-Trading before 0.1.10 constructs the swarm run directory by joining a caller-supplied run identifier onto the runs base directory without validation in run_dir (agent/src/swarm/store.py). A crafted run identifier supplied through the MCP swarm tools causes the application to read arbitrary run.json files outside the runs directory and to overwrite existing run.json files at traversed locations.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-58171?


## How do I fix CVE-2026-58171?

No fix has been published for CVE-2026-58171 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-58171 being exploited?

There is no known exploitation of CVE-2026-58171 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-58171 and fix it if it is affected.

What it is: CVE-2026-58171 is a low-severity path traversal vulnerability in HKUDS Vibe-Trading, published on 30 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-58171 in the wild and no public exploit code.

Affected product: HKUDS Vibe-Trading. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-58171/ (Markdown: https://insights.sbomify.com/CVE-2026-58171/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-58171
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-58171
- OSV: https://osv.dev/vulnerability/CVE-2026-58171

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-58171/
Summaries are generated and may contain mistakes; the official description above is the record.