CVE-2026-78212

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-24. A secondary CVSS source baseline 7.5; 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
7.5EG
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: 0.7%CVSS: 7.5Exploit: 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 Management Center versions before 20260621 as affected. No release containing a fix is confirmed on record.

4MOSAn developed by 4MOSAn Security Technology Co., Ltd. has an Arbitrary File Read vulnerability. Unauthenticated remote attackers can exploit a Relative Path Traversal flaw to download arbitrary system files.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/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)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation0.7% × 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 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 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
0.7%
EPSS %ILE
50th
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 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

August 24, 2026

Last Modified

October 12, 2026

Advisory Details (2)

Auto-updated Aug 24, 2026
No fix on record yet. Sources: cert.
CERT

4MOSAn Security Technology｜4MOSAn Management Center - Arbitrary File Read-TWCERT/CC Taiwan Computer Emergency Response Team/Coordination Center

https://www.twcert.org.tw/en/cp-139-11123-79a92-2.html
CERT

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

https://www.twcert.org.tw/tw/cp-132-11119-25dfc-1.html

Vendor Advisories for CVE-2026-78212(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 23× in last 7d / 101× 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 99 of 177 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 78 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-78212?
CVE-2026-78212 is a high-severity vulnerability; its CVE record was published on August 24, 2026. 4MOSAn developed by 4MOSAn Security Technology Co., Ltd. has an Arbitrary File Read vulnerability. Unauthenticated remote attackers can exploit a Relative Path Traversal flaw to download arbitrary system files.
When was the CVE record for CVE-2026-78212 published?
The CVE record for CVE-2026-78212 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-78212 actively exploited?
CVE-2026-78212 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (50th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-78212?
CVE-2026-78212 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-78212?
No fix for CVE-2026-78212 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 Management Center versions before 20260621 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-78212 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-78212?

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

Book a Demo →Browse All CVEs