CVE-2026-58169

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Vibe-Trading before 0.1.10 contains a DNS rebinding authentication bypass vulnerability that allows remote attackers to bypass bearer-token authentication by exploiting the server's trust of TCP peer addresses for loopback clients combined with missing Host header validation while binding to 0.0.0.0 with credentialed CORS. Attackers can craft a malicious DNS rebinding page to issue authenticated requests to the local API server, reach the shell execution endpoint with a bash-enabled preset, and achieve remote code execution as the API process user while also overwriting LLM and data-source settings to exfiltrate credentials.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
34
EG Risk 34/100

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 (value × EchelonGraph’s weight)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation0% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
34th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 30, 2026

Last Modified

July 14, 2026

Advisory Details (7)

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

Vibe-Trading < 0.1.10 - Loopback Trust and Missing Host Validation Enable DNS-Rebinding Authentication Bypass and Remote Code Execution | Advisories | VulnCheck

https://www.vulncheck.com/advisories/vibe-trading-loopback-trust-and-missing-host-validation-enable-dns-rebinding-authentication-bypass-and-remote-code-execution
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

fix: reject cross-site unsafe local API requests

Fix merged in HKUDS/Vibe-Trading PR #293 on 2026-06-23 — awaiting tagged release

https://github.com/HKUDS/Vibe-Trading/pull/293
github_pr Patch Available

[security] fix(api): require auth for settings writes

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

https://github.com/HKUDS/Vibe-Trading/pull/245
github_pr Patch Available

[security] fix(api): require explicit opt-in for agent shell tools

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

https://github.com/HKUDS/Vibe-Trading/pull/243
github_pr Patch Available

[security] fix(api): reject rebound loopback hosts

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

https://github.com/HKUDS/Vibe-Trading/pull/242
github_pr Patch Available

[security] fix(api): require explicit auth for local shutdown

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

https://github.com/HKUDS/Vibe-Trading/pull/241

Vendor Advisories for CVE-2026-58169(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 10× in last 7d / 36× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 239 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 139 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-58169?
CVE-2026-58169 is a high-severity vulnerability; its CVE record was published on June 30, 2026. Vibe-Trading before 0.1.10 contains a DNS rebinding authentication bypass vulnerability that allows remote attackers to bypass bearer-token authentication by exploiting the server's trust of TCP peer addresses for loopback clients combined with missing Host header validation while binding to…
When was CVE-2026-58169 made public?
CVE-2026-58169 was made public on June 19, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on June 30, 2026. EchelonGraph's copy of the record carries a last-modified date of July 14, 2026; the record at its source may have been updated since.
Is CVE-2026-58169 actively exploited?
CVE-2026-58169 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (34th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-58169?
CVE-2026-58169 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-58169?
A fix for CVE-2026-58169 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-58169 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-58169?

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

Book a Demo →Browse All CVEs