CVE-2026-58170

HIGHPre-NVD 8.38.3—
EchelonGraph scoreMEDIUM confidence

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.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
8.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.3Exploit: Elevated riskExposed: 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 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.

CVSS v3
8.3
EG Score
8.3(medium)
EG Risk
53(Track)
EG Risk 53/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
Severity83% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
44%
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.
github_pr Patch Available

[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/256
generic

Vibe-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-mandates
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_commit Patch Available

commit 0ab701302f90 (HKUDS/Vibe-Trading)

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

https://github.com/HKUDS/Vibe-Trading/commit/0ab701302f90e701c9dc558a898a217a376610c3

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-58170?
CVE-2026-58170 is a high vulnerability published on June 30, 2026. 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…
When was CVE-2026-58170 disclosed?
CVE-2026-58170 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-58170 actively exploited?
CVE-2026-58170 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 55.5% of all scored CVEs.
What is the CVSS score of CVE-2026-58170?
CVE-2026-58170 has a CVSS v3 base score of 8.3 (NVD).
How do I remediate CVE-2026-58170?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58170, 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-58170

Explore →

Is Your Infrastructure Affected by CVE-2026-58170?

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

Start Free Scan →Browse All CVEs