CVE-2026-58146

CRITICALPre-NVD 9.49.4
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 2.9% (87th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-80673 (ENISA EUVD) · GHSA-57h3-7px2-2q83 (GitHub Security Advisories)Source: ENISA EUVD

9.4EG
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: 2.9%CVSS: 9.4Exploit: None knownExposed services: Not assessed

The CVE record names the fixed release — apply it.

WNC T-Mobile 5G Box IDU router is vulnerable to OS command injection vulnerability. The vulnerability exists within the /cgi-bin/portal.cgi endpoint, specifically through the cli_cookie POST parameter. The cli_cookie parameter value is directly concatenated into a find command string without proper sanitization. This allows a remote, unauthenticated attacker to inject and execute arbitrary shell commands as root on the underlying operating system.

This issue has been fixed in firmware version 1.1.0.651412

CVSS
9.4
EG Score
9.4CRITICALmedium confidence
EG Risk
43
EG Risk 43/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity94% × 45%
Impact severity (EG Severity): CVSS 9.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation2.9% × 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: The CVE record names the fixed release. Apply it within your standard update timelines.
EPSS PROB
2.9%
EPSS %ILE
87th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.4): severity, escalated by confirmed exploitation. This CVE's 9.4 is its impact severity (EG Severity), not escalated.

EG Severity
9.4 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
2.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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

The CVE record names the fixed release. 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.

The score's inputs: 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

September 16, 2026

Last Modified

September 28, 2026

Advisory Details (1)

Auto-updated Oct 2, 2026
Fix named in the CVE record.
Web page

Podatności w routerach WNC T-Mobile 5G Box IDU | CERT Polska

https://cert.pl/posts/2026/09/CVE-2026-40854

Vendor Advisories for CVE-2026-58146(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 13× in last 7d / 57× 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 its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 284 rows 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 184 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-58146?
CVE-2026-58146 is a critical-severity vulnerability; its CVE record was published on September 16, 2026. WNC T-Mobile 5G Box IDU router is vulnerable to OS command injection vulnerability. The vulnerability exists within the /cgi-bin/portal.cgi endpoint, specifically through the cli_cookie POST parameter. The cli_cookie parameter value is directly concatenated into a find command string without proper…
When was the CVE record for CVE-2026-58146 published?
The CVE record for CVE-2026-58146 was published on September 16, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 28, 2026; the record at its source may have been updated since.
Is CVE-2026-58146 actively exploited?
CVE-2026-58146 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.9% probability of exploitation in the next 30 days (87th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-58146?
CVE-2026-58146 has a CVSS base score of 9.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-58146?
The CVE record for CVE-2026-58146 names the fix: "This issue has been fixed in firmware version 1.1.0.651412". The vendor advisories EchelonGraph has for CVE-2026-58146 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-58146?

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