CVE-2026-78211

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

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, ghsa, secondary
Trending — 4 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2%CVSS: 9.8Exploit: None knownExposed: 0

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

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.8(high)
EG Risk
60(Track)
EG Risk 60/100SSVC: Track

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
Severity98% × 45%
Exploitation2% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
2%
EPSS %ILE
73%
KEV
Not listed

Published

August 24, 2026

Last Modified

August 26, 2026

Advisory Details (2)

Auto-updated Aug 26, 2026
No patch confirmed 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 54× in last 7d / 54× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-08-30 01:56 UTCEG score recompute
  2. 2026-08-30 01:56 UTCGHSA enrichment
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-29 21:46 UTCGHSA enrichment
  5. 2026-08-29 17:36 UTCGHSA enrichment
  6. 2026-08-29 13:04 UTCGHSA enrichment
  7. 2026-08-29 08:52 UTCGHSA enrichment
  8. 2026-08-29 04:40 UTCGHSA enrichment
  9. 2026-08-29 00:29 UTCEG score recompute
  10. 2026-08-29 00:28 UTCGHSA enrichment
  11. 2026-08-28 21:42 UTCEPSS rescore
  12. 2026-08-28 19:25 UTCGHSA enrichment
  13. 2026-08-28 15:07 UTCGHSA enrichment
  14. 2026-08-28 10:57 UTCGHSA enrichment
  15. 2026-08-28 06:47 UTCGHSA enrichment
  16. 2026-08-28 02:36 UTCGHSA enrichment
  17. 2026-08-27 22:26 UTCGHSA enrichment
  18. 2026-08-27 18:16 UTCEG score recompute
  19. 2026-08-27 18:16 UTCGHSA enrichment
  20. 2026-08-27 14:25 UTCEPSS rescore
  21. 2026-08-27 13:59 UTCGHSA enrichment
  22. 2026-08-27 09:48 UTCGHSA enrichment
  23. 2026-08-27 05:36 UTCGHSA enrichment
  24. 2026-08-27 01:22 UTCGHSA enrichment
  25. 2026-08-26 21:11 UTCGHSA enrichment
Show 29 more
  1. 2026-08-26 17:00 UTCGHSA enrichment
  2. 2026-08-26 16:13 UTCEG score recompute
  3. 2026-08-26 16:13 UTCGHSA enrichment
  4. 2026-08-26 14:47 UTCEPSS rescore
  5. 2026-08-26 11:42 UTCGHSA enrichment
  6. 2026-08-26 07:32 UTCGHSA enrichment
  7. 2026-08-26 03:21 UTCGHSA enrichment
  8. 2026-08-25 23:10 UTCGHSA enrichment
  9. 2026-08-25 18:41 UTCGHSA enrichment
  10. 2026-08-25 14:31 UTCEG score recompute
  11. 2026-08-25 14:31 UTCGHSA enrichment
  12. 2026-08-25 13:49 UTCEPSS rescore
  13. 2026-08-25 10:21 UTCGHSA enrichment
  14. 2026-08-25 06:11 UTCGHSA enrichment
  15. 2026-08-25 01:59 UTCGHSA enrichment
  16. 2026-08-24 21:49 UTCGHSA enrichment
  17. 2026-08-24 17:38 UTCEG score recompute
  18. 2026-08-24 17:38 UTCGHSA enrichment
  19. 2026-08-24 14:18 UTCEPSS rescore
  20. 2026-08-24 13:28 UTCEG score recompute
  21. 2026-08-24 13:28 UTCGHSA enrichment
  22. 2026-08-24 12:59 UTCEG score recompute
  23. 2026-08-24 12:59 UTCGHSA enrichment
  24. 2026-08-24 12:44 UTCGHSA enrichment
  25. 2026-08-24 08:34 UTCEG score recompute
  26. 2026-08-24 08:34 UTCGHSA enrichment
  27. 2026-08-24 04:23 UTCEG score recompute
  28. 2026-08-24 03:51 UTCEG score recompute
  29. 2026-08-24 03:50 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-78211?
CVE-2026-78211 is a critical vulnerability 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 CVE-2026-78211 disclosed?
CVE-2026-78211 was first published in the National Vulnerability Database on August 24, 2026, with the most recent update on August 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-78211 actively exploited?
CVE-2026-78211 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2% probability of exploitation in the next 30 days, which ranks it in the top 27.2% of all scored CVEs.
What is the CVSS score of CVE-2026-78211?
CVE-2026-78211 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-78211?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-78211, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs