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.
CVE-2026-58170
Score 8.3 from GitHub Security Advisory (severity: HIGH) published 2026-06-30. a secondary CVSS source baseline 8.3; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.3
- EG Score
- 8.3(high)
- EPSS
- 33.5%
- KEV
- Not listed
Published
June 30, 2026
Last Modified
July 1, 2026
Advisory Details (4)
Auto-updated Jun 30, 2026[security] fix(live): contain mandate proposal identifiers
Patch available: HKUDS/Vibe-Trading v0.1.10 (PR #256 merged 2026-06-18)
https://github.com/HKUDS/Vibe-Trading/pull/256Vibe-Trading < 0.1.10 - Path Traversal in Proposal Identifier Allows Forging Live Trading Mandates | Advisories | VulnCheck
https://www.vulncheck.com/advisories/vibe-trading-path-traversal-in-proposal-identifier-allows-forging-live-trading-mandatesv0.1.10 — Global data layer + roll-up since 0.1.9
Patch available: HKUDS/Vibe-Trading v0.1.10
https://github.com/HKUDS/Vibe-Trading/releases/tag/v0.1.10commit 0ab701302f90 (HKUDS/Vibe-Trading)
Patch available: HKUDS/Vibe-Trading v0.1.10 (contains commit 0ab701302f90)
https://github.com/HKUDS/Vibe-Trading/commit/0ab701302f90e701c9dc558a898a217a376610c3Vendor Advisories for CVE-2026-58170(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 38× in last 7d / 38× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-06 21:47 UTCEG score recompute
- 2026-07-06 21:47 UTCGHSA enrichment
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 10:29 UTCEG score recompute
- 2026-07-06 10:29 UTCGHSA enrichment
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 23:10 UTCEG score recompute
- 2026-07-05 23:10 UTCGHSA enrichment
- 2026-07-05 11:46 UTCEG score recompute
- 2026-07-05 11:46 UTCGHSA enrichment
- 2026-07-05 02:31 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-05 00:27 UTCEG score recompute
- 2026-07-05 00:27 UTCGHSA enrichment
- 2026-07-04 13:08 UTCEG score recompute
- 2026-07-04 13:08 UTCGHSA enrichment
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 01:50 UTCEG score recompute
- 2026-07-04 01:50 UTCGHSA enrichment
- 2026-07-03 14:30 UTCEG score recompute
- 2026-07-03 14:30 UTCGHSA enrichment
- 2026-07-03 03:11 UTCEG score recompute
Show 13 moreShow fewer
- 2026-07-03 03:11 UTCGHSA enrichment
- 2026-07-02 15:50 UTCEG score recompute
- 2026-07-02 15:50 UTCGHSA enrichment
- 2026-07-02 04:32 UTCEG score recompute
- 2026-07-02 04:31 UTCGHSA enrichment
- 2026-07-01 17:13 UTCEG score recompute
- 2026-07-01 17:13 UTCGHSA enrichment
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-07-01 05:54 UTCEG score recompute
- 2026-07-01 05:54 UTCGHSA enrichment
- 2026-06-30 18:33 UTCEG score recompute
- 2026-06-30 18:33 UTCGHSA enrichment
- 2026-06-30 18:32 UTCNVD updatefirst tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-58170?
When was CVE-2026-58170 disclosed?
Is CVE-2026-58170 actively exploited?
What is the CVSS score of CVE-2026-58170?
How do I remediate CVE-2026-58170?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-58170
Is Your Infrastructure Affected by CVE-2026-58170?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.