CVE-2026-58171

MEDIUMPre-NVD 4.24.2—
EchelonGraph scoreHIGH confidence

Score 4.2 from GitHub Security Advisory (severity: LOW) published 2026-06-30. a secondary CVSS source baseline 4.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
4.2
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.2Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Vibe-Trading before 0.1.10 constructs the swarm run directory by joining a caller-supplied run identifier onto the runs base directory without validation in run_dir (agent/src/swarm/store.py). A crafted run identifier supplied through the MCP swarm tools causes the application to read arbitrary run.json files outside the runs directory and to overwrite existing run.json files at traversed locations.

CVSS v3
4.2
EG Score
4.2(high)
EPSS
16.7%
KEV
Not listed

Published

June 30, 2026

Last Modified

July 1, 2026

Advisory Details (4)

Auto-updated Jun 30, 2026
Patch available. Sources: github_pr, github_release, github_commit.
generic

Vibe-Trading < 0.1.10 - Path Traversal via Swarm Run Identifier | Advisories | VulnCheck

https://www.vulncheck.com/advisories/vibe-trading-path-traversal-via-swarm-run-identifier
github_release Patch Available

v0.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.10
github_pr Patch Available

[security] fix(mcp): contain swarm run identifiers

Patch available: HKUDS/Vibe-Trading v0.1.10 (PR #258 merged 2026-06-18)

https://github.com/HKUDS/Vibe-Trading/pull/258
github_commit Patch Available

commit f45fd85392f0 (HKUDS/Vibe-Trading)

Patch available: HKUDS/Vibe-Trading v0.1.10 (contains commit f45fd85392f0)

https://github.com/HKUDS/Vibe-Trading/commit/f45fd85392f07b5e404e41d4fcb0ef0d6c2f87ab

Vendor Advisories for CVE-2026-58171(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.

  1. 2026-07-07 05:47 UTCEG score recompute
  2. 2026-07-07 05:46 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 03:54 UTCEG score recompute
  6. 2026-07-06 03:54 UTCGHSA enrichment
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 02:31 UTCEPSS rescore
  10. 2026-07-05 02:30 UTCEPSS rescore
  11. 2026-07-05 02:02 UTCEG score recompute
  12. 2026-07-05 02:02 UTCGHSA enrichment
  13. 2026-07-04 06:31 UTCEPSS rescore
  14. 2026-07-04 06:31 UTCEPSS rescore
  15. 2026-07-04 00:09 UTCEG score recompute
  16. 2026-07-04 00:09 UTCGHSA enrichment
  17. 2026-07-02 22:18 UTCEG score recompute
  18. 2026-07-02 22:18 UTCGHSA enrichment
  19. 2026-07-01 20:25 UTCEG score recompute
  20. 2026-07-01 20:25 UTCGHSA enrichment
  21. 2026-07-01 15:07 UTCEPSS rescore
  22. 2026-06-30 18:33 UTCEG score recompute
  23. 2026-06-30 18:33 UTCGHSA enrichment
  24. 2026-06-30 18:32 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-58171?
CVE-2026-58171 is a medium vulnerability published on June 30, 2026. Vibe-Trading before 0.1.10 constructs the swarm run directory by joining a caller-supplied run identifier onto the runs base directory without validation in run_dir (agent/src/swarm/store.py). A crafted run identifier supplied through the MCP swarm tools causes the application to read arbitrary…
When was CVE-2026-58171 disclosed?
CVE-2026-58171 was first published in the National Vulnerability Database on June 30, 2026, with the most recent update on July 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-58171 actively exploited?
CVE-2026-58171 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 16.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-58171?
CVE-2026-58171 has a CVSS v3 base score of 4.2 (NVD).
How do I remediate CVE-2026-58171?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58171, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-58171

Explore →

Is Your Infrastructure Affected by CVE-2026-58171?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs