Quick answers
- Is CVE-2026-58171 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-58171 being exploited in the wild.
- How severe is CVE-2026-58171?
- Medium severity, with a CVSS score of 4.2, published 30 June 2026.
- Which products and versions are affected?
- HKUDS Vibe-Trading < 0.1.10.
- Is there a fix for CVE-2026-58171?
- A patch was published on 2026-06-18: Fix merged in pull request #258 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-58171 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-58171?
- Check whether you run HKUDS Vibe-Trading at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A path traversal vulnerability exists in Vibe-Trading's swarm storage logic (agent/src/swarm/store.py). The `run_dir` function constructs filesystem paths by joining a base directory with a caller-supplied `run_id` without proper sanitization or validation. An attacker with access to the Model Context Protocol (MCP) swarm tools can provide a crafted `run_id` (e.g., using '../' sequences) to access or overwrite `run.json` files outside the designated `.swarm/runs` directory. While the impact is limited to locations containing parseable `run.json` files, it allows for unauthorized modification of swarm artifacts and state. The issue is fixed in version 0.1.10 by enforcing that run identifiers are bare strings without path separators.
Affected products
- HKUDS Vibe-Trading < 0.1.10
Timeline
- 2026-06-18: patched: Fix merged in pull request #258
- 2026-06-19: advisory: Official release of v0.1.10 containing the fix
- 2026-06-30: disclosed: CVE-2026-58171 published