CVE-2026-47786

CRITICALPre-NVD 9.39.3
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 1.1% (65th 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-101989 (ENISA EUVD) · GHSA-m358-vx46-jcm4 (GitHub Security Advisories)Source: ENISA EUVD

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

We have already fixed the vulnerability in the following version: HybridDesk Station 4.2.23 and later (from the CVE record's solution, QNAP Systems, Inc.) — apply it.

An OS command injection vulnerability has been reported to affect HybridDesk Station. If exploited, the vulnerability could allow remote attackers to execute arbitrary commands.

We have already fixed the vulnerability in the following version: HybridDesk Station 4.2.23 and later HybridDesk Station 4.3.4 and later

CVSS
9.3
EG Score
9.3CRITICALmedium confidence
EG Risk
57
EG Risk 57/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)
Severity93% × 45%
Impact severity (EG Severity): CVSS 9.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation1.1% × 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: We have already fixed the vulnerability in the following version: HybridDesk Station 4.2.23 and later (from the CVE record's solution, QNAP Systems, Inc.). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
1.1%
EPSS %ILE
65th
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.3): severity, escalated by confirmed exploitation. This CVE's 9.3 is its impact severity (EG Severity), not escalated.

EG Severity
9.3 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
1.1% 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; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days 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; Attend at high (mission-essential systems).

We have already fixed the vulnerability in the following version: HybridDesk Station 4.2.23 and later (from the CVE record's solution, QNAP Systems, Inc.). 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 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)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

October 15, 2026

Last Modified

October 15, 2026

Vendor Advisories for CVE-2026-47786(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 15× in last 7d / 64× 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.

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

Frequently asked(5)

What is CVE-2026-47786?
CVE-2026-47786 is a critical-severity vulnerability; its CVE record was published on October 15, 2026. An OS command injection vulnerability has been reported to affect HybridDesk Station. If exploited, the vulnerability could allow remote attackers to execute arbitrary commands. We have already fixed the vulnerability in the following version: HybridDesk Station 4.2.23 and later HybridDesk Station…
When was the CVE record for CVE-2026-47786 published?
The CVE record for CVE-2026-47786 was published on October 15, 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 October 15, 2026; the record at its source may have been updated since.
Is CVE-2026-47786 actively exploited?
CVE-2026-47786 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.1% probability of exploitation in the next 30 days (65th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-47786?
CVE-2026-47786 has a CVSS base score of 9.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-47786?
The CVE record's solution for CVE-2026-47786, written by its CNA QNAP Systems, Inc., names the fix: "We have already fixed the vulnerability in the following version: HybridDesk Station 4.2.23 and later". The vendor advisories EchelonGraph has for CVE-2026-47786 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-47786?

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