Quick answers
- Is CVE-2026-58173 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-58173 being exploited in the wild.
- How severe is CVE-2026-58173?
- Medium severity, with a CVSS score of 6.5, published 30 June 2026.
- Which products and versions are affected?
- HKUDS Vibe-Trading < 0.1.10.
- Is there a fix for CVE-2026-58173?
- A patch was published on 2026-06-19: Version 0.1.10 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-58173 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-58173?
- 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 PersistentMemory.add() function and the associated RememberTool. The application fails to validate the 'memory_type' parameter, which is used as a prefix in filename construction (e.g., f"{memory_type}_{slug}.md"). An authenticated attacker can provide a 'memory_type' containing traversal sequences (like '../') to escape the configured memory root directory. While the 'slug' portion of the filename is sanitized, the prefix is not, allowing arbitrary Markdown and frontmatter files to be written or overwritten anywhere the application has write permissions. This issue was addressed in version 0.1.10 by implementing a strict allowlist for memory categories.
Affected products
- HKUDS Vibe-Trading < 0.1.10
Timeline
- 2026-06-18: disclosed: Fix PR submitted to GitHub repository
- 2026-06-19: patched: Version 0.1.10 released
- 2026-06-30: advisory: CVE-2026-58173 published