CVE-2017-20236

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-04-04. A secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
9.8EG
EchelonGraph verdictPlan mitigationRemediate 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.7%CVSS: 9.8Exploit: None knownExposed services: Not assessed

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

ProSoft Technology ICX35-HWC versions 1.3 and prior cellular gateways contain an input validation vulnerability in the web user interface that allows remote attackers to inject and execute system commands by submitting malicious input through unvalidated fields. Attackers can exploit this vulnerability to gain root privileges and execute arbitrary commands on the device through the accessible web interface.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/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)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation0.7% × 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 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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.7%
EPSS %ILE
51st
KEV
Not listed

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

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable yes (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

Published

April 3, 2026

Last Modified

July 21, 2026

Advisory Details (2)

Auto-updated Oct 10, 2026
No fix on record yet.
Web page

ProSoft Technology ICX35-HWC Command Injection via Web Interface | Advisories | VulnCheck

https://www.vulncheck.com/advisories/prosoft-technology-icx35-hwc-command-injection-via-web-interface
Web page
https://assets.belden.com/m/1116a05ab702b2ba/original/Security-Bulletin-User-Interface-ProSoft-ICX35-BSECV-2017-10.pdf

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 20× 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 97 of 228 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. 3 repeat rows among the latest 100 are merged into the row they repeat. The 131 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2017-20236?
CVE-2017-20236 is a critical-severity vulnerability; its CVE record was published on April 3, 2026. ProSoft Technology ICX35-HWC versions 1.3 and prior cellular gateways contain an input validation vulnerability in the web user interface that allows remote attackers to inject and execute system commands by submitting malicious input through unvalidated fields. Attackers can exploit this…
When was CVE-2017-20236 made public?
CVE-2017-20236 was made public on May 8, 2017: 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 April 3, 2026. EchelonGraph's copy of the record carries a last-modified date of July 21, 2026; the record at its source may have been updated since.
Is CVE-2017-20236 actively exploited?
CVE-2017-20236 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (51st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2017-20236?
CVE-2017-20236 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2017-20236?
No fix for CVE-2017-20236 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2017-20236

Explore →

Is Your Infrastructure Affected by CVE-2017-20236?

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

Book a Demo →Browse All CVEs