CVE-2026-38059

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.5Exploit: None knownExposed services: Not assessed

ST Engineering iDirect has fixed the vulnerabilities and recommend users update the software to version 4.5.3.0 or newer (from the CVE record's solution, Cybersecurity and Infrastructure Security Agency (CISA) Industrial Control Systems (ICS)) — apply it.

The iDirect iQ200 exposes the /api/identity and /api/ REST API endpoints without authentication. An unauthenticated attacker with network access can retrieve sensitive device information including the serial number, Device ID (DID), Terminal Private Key identifier (TPK), MAC address, and exact firmware version. The DID and TPK are used for satellite network authentication in the iDirect platform, potentially enabling terminal impersonation and network reconnaissance.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/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.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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: ST Engineering iDirect has fixed the vulnerabilities and recommend users update the software to version 4.5.3.0 or newer (from the CVE record's solution, Cybersecurity and Infrastructure Security Agency (CISA) Industrial Control Systems (ICS)). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
46th
KEV
Not listed

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

ST Engineering iDirect has fixed the vulnerabilities and recommend users update the software to version 4.5.3.0 or newer (from the CVE record's solution, Cybersecurity and Infrastructure Security Agency (CISA) Industrial Control Systems (ICS)). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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

July 10, 2026

Last Modified

September 11, 2026

Advisory Details (2)

Auto-updated Jul 10, 2026
Fix named in the CVE record's solution (Cybersecurity and Infrastructure Security Agency (CISA) Industrial Control Systems (ICS)). Sources: cisa.
CISA

ST Engineering iDirect iQ-Series Terminals | CISA

https://www.cisa.gov/news-events/ics-advisories/icsa-26-183-01
Web page

CSAF/csaf_files/OT/white/2026/icsa-26-183-01.json at develop · cisagov/CSAF · GitHub

https://github.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-183-01.json

Vendor Advisories for CVE-2026-38059(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 11× in last 7d / 37× 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 99 of 238 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 139 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-38059?
CVE-2026-38059 is a high-severity vulnerability; its CVE record was published on July 10, 2026. The iDirect iQ200 exposes the /api/identity and /api/ REST API endpoints without authentication. An unauthenticated attacker with network access can retrieve sensitive device information including the serial number, Device ID (DID), Terminal Private Key identifier (TPK), MAC address, and exact…
When was CVE-2026-38059 made public?
CVE-2026-38059 was made public on July 2, 2026: that is the date its CVE record's CNA, Cybersecurity and Infrastructure Security Agency (CISA) Industrial Control Systems (ICS), gives for when the vulnerability was made public. The CVE record itself was published on July 10, 2026. EchelonGraph's copy of the record carries a last-modified date of September 11, 2026; the record at its source may have been updated since.
Is CVE-2026-38059 actively exploited?
CVE-2026-38059 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (46th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-38059?
CVE-2026-38059 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-38059?
The CVE record's solution for CVE-2026-38059, written by its CNA Cybersecurity and Infrastructure Security Agency (CISA) Industrial Control Systems (ICS), names the fix: "ST Engineering iDirect has fixed the vulnerabilities and recommend users update the software to version 4.5.3.0 or newer." The vendor advisories EchelonGraph has for CVE-2026-38059 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-38059?

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