CVE-2026-5573

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.5% (44th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 7.3 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-04-05) is not newer than that change (2026-07-24), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-19095 (ENISA EUVD) · GHSA-mfwc-7h58-p642 (GitHub Security Advisories)Source: ENISA EUVD

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).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

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

A weakness has been identified in Technostrobe HI-LED-WR120-G2 5.5.0.1R6.03.30. This impacts an unknown function of the file /fs. Executing a manipulation of the argument cwd can lead to unrestricted upload. The attack can be launched remotely. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
75
EG Risk 75/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
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 public PoC (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: No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines at low or medium mission impact and sooner than that at high, and watch for a fix.
EPSS PROB
0.5%
EPSS %ILE
44th
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.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). 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; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

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 within your standard update timelines at low or medium mission impact and sooner than that at high, and watch for a fix.

Exploitation public PoC (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

April 5, 2026

Last Modified

July 24, 2026

Advisory Details (1)

Auto-updated Oct 17, 2026
🔬 Proof of concept available. No fix on record yet.
Web page🟡 PoC Available

my--cve-vulnerability-research/my_VulnDB_cves/CVE-TECHNOSTROBE-05-FileUpload.md at main · shiky8/my--cve-vulnerability-research · GitHub

https://github.com/shiky8/my--cve-vulnerability-research/blob/main/my_VulnDB_cves/CVE-TECHNOSTROBE-05-FileUpload.md

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 23× in last 7d / 72× 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 286 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 186 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-5573?
CVE-2026-5573 is a critical-severity vulnerability; its CVE record was published on April 5, 2026. A weakness has been identified in Technostrobe HI-LED-WR120-G2 5.5.0.1R6.03.30. This impacts an unknown function of the file /fs. Executing a manipulation of the argument cwd can lead to unrestricted upload. The attack can be launched remotely. The exploit has been made available to the public and…
When was the CVE record for CVE-2026-5573 published?
The CVE record for CVE-2026-5573 was published on April 5, 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 July 24, 2026; the record at its source may have been updated since.
Is CVE-2026-5573 actively exploited?
CVE-2026-5573 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-5573?
CVE-2026-5573 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-5573?
No fix for CVE-2026-5573 is confirmed yet. Until one is published, restrict network exposure of the affected system — for example, keep it off the internet or limit it to trusted networks — and watch for a fix.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-5573?

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

Book a Demo →Browse All CVEs