CVE-2026-78211

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-08-24. 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
Trending — 3 sources updated this week
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: 2.0%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.

The CVE record's CNA (TWCERT/CC) lists 4MOSAn Security Technology 4MOSAn GCB Doctor versions before 20260621 as affected. No release containing a fix is confirmed on record.

4MOSAn GCB Doctor developed by 4MOSAn Security Technology has a OS Command Injection vulnerability. Unauthenticated remote attackers can inject malicious commands through an unremoved ADOdb test page parameter, thereby executing arbitrary system commands on the server.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
60
EG Risk 60/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.
Exploitation2.0% × 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
2.0%
EPSS %ILE
80th
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

BOD 26-04 (CISA's remediation timeline, Table 1)3 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 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

August 24, 2026

Last Modified

October 12, 2026

Advisory Details (2)

Auto-updated Oct 13, 2026
No fix on record yet. Sources: cert.
CERT

美麗島安全科技｜4MOSAn GCB Doctor - OS Command Injection-TWCERT/CC台灣電腦網路危機處理暨協調中心|企業資安通報協處|資安情資分享|漏洞通報|資安聯盟|資安電子報

https://www.twcert.org.tw/tw/cp-132-11118-dfee4-1.html
CERT

4MOSAn Security Technology｜4MOSAn GCB Doctor - OS Command Injection-TWCERT/CC Taiwan Computer Emergency Response Team/Coordination Center

https://www.twcert.org.tw/en/cp-139-11122-3d95a-2.html

Vendor Advisories for CVE-2026-78211(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 22× in last 7d / 176× 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 339 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 239 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-78211?
CVE-2026-78211 is a critical-severity vulnerability; its CVE record was published on August 24, 2026. 4MOSAn GCB Doctor developed by 4MOSAn Security Technology has a OS Command Injection vulnerability. Unauthenticated remote attackers can inject malicious commands through an unremoved ADOdb test page parameter, thereby executing arbitrary system commands on the server.
When was the CVE record for CVE-2026-78211 published?
The CVE record for CVE-2026-78211 was published on August 24, 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 12, 2026; the record at its source may have been updated since.
Is CVE-2026-78211 actively exploited?
CVE-2026-78211 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.0% probability of exploitation in the next 30 days (80th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-78211?
CVE-2026-78211 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-2026-78211?
No fix for CVE-2026-78211 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. The CVE record's CNA (TWCERT/CC) lists 4MOSAn Security Technology 4MOSAn GCB Doctor versions before 20260621 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-78211 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-78211?

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

Book a Demo →Browse All CVEs