Vibe-Trading before 0.1.10 contains a path traversal vulnerability that allows attackers to write files outside the intended memory root directory by supplying a malicious memory_type value containing path traversal sequences through the remember tool. Attackers can manipulate the memory_type parameter in the persistent memory store to cause the application to write arbitrary Markdown files to unintended locations on the filesystem.
CVE-2026-58173
Score 6.5 from GitHub Security Advisory published 2026-06-30. a secondary CVSS source baseline 6.5; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(high)
- EPSS
- 22.5%
- KEV
- Not listed
Published
June 30, 2026
Last Modified
July 1, 2026
Advisory Details (3)
Auto-updated Jun 30, 2026[security] fix(memory): validate persistent memory types
Patch available: HKUDS/Vibe-Trading v0.1.10 (PR #257 merged 2026-06-18)
https://github.com/HKUDS/Vibe-Trading/pull/257Vibe-Trading < 0.1.10 - Path Traversal via Persistent Memory Type | Advisories | VulnCheck
https://www.vulncheck.com/advisories/vibe-trading-path-traversal-via-persistent-memory-typev0.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.10Vendor Advisories for CVE-2026-58173(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 24× in last 7d / 24× 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 22:42 UTCEG score recompute
- 2026-07-06 22:42 UTCGHSA enrichment
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 22:01 UTCEG score recompute
- 2026-07-05 22:01 UTCGHSA enrichment
- 2026-07-05 02:31 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 21:19 UTCEG score recompute
- 2026-07-04 21:18 UTCGHSA enrichment
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-03 20:37 UTCEG score recompute
- 2026-07-03 20:37 UTCGHSA enrichment
- 2026-07-02 19:56 UTCEG score recompute
- 2026-07-02 19:56 UTCGHSA enrichment
- 2026-07-01 19:15 UTCEG score recompute
- 2026-07-01 19:15 UTCGHSA enrichment
- 2026-07-01 15:07 UTCEPSS rescore
- 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-58173?
When was CVE-2026-58173 disclosed?
Is CVE-2026-58173 actively exploited?
What is the CVSS score of CVE-2026-58173?
How do I remediate CVE-2026-58173?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-58173
Is Your Infrastructure Affected by CVE-2026-58173?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.