CVE-2026-58171

MEDIUMPre-NVD 4.24.2—
EchelonGraph scoreMEDIUM 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 — 3 sources updated this week
4.2EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.2Exploit: None knownExposed: 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(medium)
EG Risk
19(Track)
EG Risk 19/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity42% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
28%
KEV
Not listed

Published

June 30, 2026

Last Modified

July 14, 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 7× in last 7d / 53× 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.

Showing the most recent 100 of 160 total refreshes for this CVE.

  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-10 09:35 UTCEPSS rescore
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-07 16:01 UTCEPSS rescore
  5. 2026-09-06 14:36 UTCEG score recompute
  6. 2026-09-06 14:36 UTCGHSA enrichment
  7. 2026-09-06 13:47 UTCEPSS rescore
  8. 2026-09-04 05:07 UTCEPSS rescore
  9. 2026-09-02 14:12 UTCEPSS rescore
  10. 2026-09-01 13:54 UTCEPSS rescore
  11. 2026-09-01 04:40 UTCEPSS rescore
  12. 2026-08-30 19:17 UTCEPSS rescore
  13. 2026-08-30 18:03 UTCEG score recompute
  14. 2026-08-30 18:03 UTCGHSA enrichment
  15. 2026-08-30 01:22 UTCEPSS rescore
  16. 2026-08-28 21:42 UTCEPSS rescore
  17. 2026-08-27 22:41 UTCEG score recompute
  18. 2026-08-27 22:41 UTCGHSA enrichment
  19. 2026-08-27 14:25 UTCEPSS rescore
  20. 2026-08-26 14:46 UTCEPSS rescore
  21. 2026-08-25 13:49 UTCEPSS rescore
  22. 2026-08-24 12:59 UTCEG score recompute
  23. 2026-08-24 12:59 UTCGHSA enrichment
  24. 2026-08-23 11:07 UTCEG score recompute
  25. 2026-08-23 11:07 UTCGHSA enrichment
Show 75 more
  1. 2026-08-23 00:19 UTCEPSS rescore
  2. 2026-08-22 09:16 UTCEG score recompute
  3. 2026-08-22 09:16 UTCGHSA enrichment
  4. 2026-08-21 23:49 UTCEPSS rescore
  5. 2026-08-21 07:24 UTCEG score recompute
  6. 2026-08-21 07:24 UTCGHSA enrichment
  7. 2026-08-20 22:55 UTCEPSS rescore
  8. 2026-08-20 05:32 UTCEG score recompute
  9. 2026-08-20 05:32 UTCGHSA enrichment
  10. 2026-08-19 17:04 UTCEPSS rescore
  11. 2026-08-18 23:01 UTCEG score recompute
  12. 2026-08-18 23:01 UTCGHSA enrichment
  13. 2026-08-18 13:48 UTCEPSS rescore
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-17 13:09 UTCEG score recompute
  16. 2026-08-17 13:09 UTCGHSA enrichment
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 11:16 UTCEG score recompute
  19. 2026-08-16 11:16 UTCGHSA enrichment
  20. 2026-08-16 02:14 UTCEPSS rescore
  21. 2026-08-15 09:25 UTCEG score recompute
  22. 2026-08-15 09:25 UTCGHSA enrichment
  23. 2026-08-15 01:30 UTCEPSS rescore
  24. 2026-08-14 07:32 UTCEG score recompute
  25. 2026-08-14 07:32 UTCGHSA enrichment
  26. 2026-08-13 22:00 UTCEPSS rescore
  27. 2026-08-13 05:41 UTCEG score recompute
  28. 2026-08-13 05:41 UTCGHSA enrichment
  29. 2026-08-12 13:51 UTCEPSS rescore
  30. 2026-08-12 03:49 UTCEG score recompute
  31. 2026-08-12 03:49 UTCGHSA enrichment
  32. 2026-08-11 01:57 UTCEG score recompute
  33. 2026-08-11 01:57 UTCGHSA enrichment
  34. 2026-08-11 00:00 UTCEPSS rescore
  35. 2026-08-10 00:05 UTCEG score recompute
  36. 2026-08-10 00:05 UTCGHSA enrichment
  37. 2026-08-09 13:46 UTCEPSS rescore
  38. 2026-08-08 22:14 UTCEG score recompute
  39. 2026-08-08 22:14 UTCGHSA enrichment
  40. 2026-08-08 16:37 UTCEPSS rescore
  41. 2026-08-07 20:22 UTCEG score recompute
  42. 2026-08-07 20:22 UTCGHSA enrichment
  43. 2026-08-06 18:31 UTCEG score recompute
  44. 2026-08-06 18:31 UTCGHSA enrichment
  45. 2026-08-06 13:47 UTCEPSS rescore
  46. 2026-08-05 19:17 UTCEPSS rescore
  47. 2026-08-05 16:40 UTCEG score recompute
  48. 2026-08-05 16:40 UTCGHSA enrichment
  49. 2026-08-04 15:10 UTCEPSS rescore
  50. 2026-08-04 10:39 UTCEPSS rescore
  51. 2026-08-04 08:52 UTCEG score recompute
  52. 2026-08-04 08:52 UTCGHSA enrichment
  53. 2026-08-03 10:36 UTCEPSS rescore
  54. 2026-08-03 07:00 UTCGHSA enrichment
  55. 2026-08-02 04:04 UTCEG score recompute
  56. 2026-08-02 04:04 UTCGHSA enrichment
  57. 2026-08-02 02:27 UTCEPSS rescore
  58. 2026-08-01 04:16 UTCEPSS rescore
  59. 2026-08-01 02:12 UTCGHSA enrichment
  60. 2026-07-31 00:18 UTCEG score recompute
  61. 2026-07-31 00:17 UTCGHSA enrichment
  62. 2026-07-30 16:28 UTCEPSS rescore
  63. 2026-07-30 01:30 UTCEPSS rescore
  64. 2026-07-30 01:30 UTCEPSS rescore
  65. 2026-07-29 22:21 UTCGHSA enrichment
  66. 2026-07-28 19:13 UTCEG score recompute
  67. 2026-07-28 19:13 UTCGHSA enrichment
  68. 2026-07-28 15:37 UTCEPSS rescore
  69. 2026-07-27 16:50 UTCEG score recompute
  70. 2026-07-27 16:50 UTCGHSA enrichment
  71. 2026-07-27 14:14 UTCEPSS rescore
  72. 2026-07-26 14:54 UTCEPSS rescore
  73. 2026-07-26 14:54 UTCEPSS rescore
  74. 2026-07-26 13:52 UTCEG score recompute
  75. 2026-07-26 13:52 UTCGHSA enrichment

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 14, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 72.5% of all scored CVEs.
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