CVE-2026-58170
Vibe-Trading before 0.1.10 builds the proposal file path by joining …
Vibe-Trading before 0.1.10 builds the proposal file path by joining a caller-supplied proposal identifier onto the broker proposals directory without sanitization (agent/src/live/mandate/commit.py). A proposal identifier containing path traversal sequences causes the application to load an attacker-controlled JSON file as an authoritative live trading mandate. Combined with the file upload endpoint, an admitted caller can write a JSON file to a known location and traverse to it, and because the ceilings validation is skipped when ceilings are absent, the attacker fully controls the committed mandate.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/HKUDS/Vibe-Trading/commit/0ab701302f90e701c9dc558a898a217a376610c3
- github.com/HKUDS/Vibe-Trading/pull/256
- github.com/HKUDS/Vibe-Trading/releases/tag/v0.1.10
- www.vulncheck.com/advisories/vibe-trading-path-traversal-in-proposal-identifier-allows-for
- nvd.nist.gov/vuln/detail/CVE-2026-58170
- cve.org/CVERecord?id=CVE-2026-58170
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.