CVE-2025-30047

CRITICALPre-NVD 9.49.4
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (32nd 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-2025-211178 (ENISA EUVD) · GHSA-hjw9-7f25-8h43 (GitHub Security Advisories)Source: ENISA EUVD

9.4EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 9.4Exploit: None knownExposed services: Not assessed

The CVE record names the fixed release — apply it.

CGM CLININET is vulnerable to Remote Code Execution caused by deserialization of untrusted data. The server exposes an HTTP-based API, used by the administrative module, that exchanges data using Java object serialization. An attacker within the same local network is able to send requests to this API and transmit a crafted serialized object. When it is deserialized, it allows arbitrary code execution with root privileges on the server. 

This issue was fixed in version 2026.MS3

CVSS
9.4
EG Score
9.4CRITICALmedium confidence
EG Risk
42
EG Risk 42/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)
Severity94% × 45%
Impact severity (EG Severity): CVSS 9.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (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: The CVE record names the fixed release. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
32nd
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.4): severity, escalated by confirmed exploitation. This CVE's 9.4 is its impact severity (EG Severity), not escalated.

EG Severity
9.4 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.4% 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; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade 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; Track* at high (mission-essential systems).

The CVE record names the fixed release. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

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

Last Modified

October 28, 2026

Advisory Details (2)

Auto-updated Oct 23, 2026
Fix named in the CVE record.
Web page

Szpitalny system informacyjny HIS – CGM CLININET | CGM

https://www.cgm.com/pol_pl/products/szpital/cgm-clininet.html
Web pageMentions a patch (unverified)

Vulnerabilities in CGM CLININET software | CERT Polska

https://cert.pl/en/posts/2026/10/CVE-2025-30043/

Vendor Advisories for CVE-2025-30047(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 / 48× 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-13 16:49 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  2. 2026-11-13 04:23 UTCEchelonGraph re-scored
  3. 2026-11-13 04:23 UTCGHSA enrichmentGHSA-hjw9-7f25-8h43 · GitHub severity CRITICAL
  4. 2026-11-12 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  5. 2026-11-12 03:20 UTCEchelonGraph re-scored
  6. 2026-11-12 03:20 UTCGHSA enrichmentGHSA-hjw9-7f25-8h43 · GitHub severity CRITICAL
  7. 2026-11-11 16:36 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  8. 2026-11-11 02:23 UTCGHSA enrichmentGHSA-hjw9-7f25-8h43 · GitHub severity CRITICAL
  9. 2026-11-11 01:02 UTCEchelonGraph re-scored
  10. 2026-11-11 01:02 UTCGHSA enrichmentGHSA-hjw9-7f25-8h43 · GitHub severity CRITICAL
  11. 2026-11-10 16:40 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  12. 2026-11-10 00:05 UTCEchelonGraph re-scored
  13. 2026-11-10 00:05 UTCGHSA enrichmentGHSA-hjw9-7f25-8h43 · GitHub severity CRITICAL
  14. 2026-11-09 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  15. 2026-11-08 23:08 UTCEchelonGraph re-scored
  16. 2026-11-08 23:08 UTCGHSA enrichmentGHSA-hjw9-7f25-8h43 · GitHub severity CRITICAL
  17. 2026-11-08 16:36 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  18. 2026-11-07 22:11 UTCEchelonGraph re-scored
  19. 2026-11-07 22:11 UTCGHSA enrichmentGHSA-hjw9-7f25-8h43 · GitHub severity CRITICAL
  20. 2026-11-07 16:36 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  21. 2026-11-06 21:10 UTCEchelonGraph re-scored
  22. 2026-11-06 21:10 UTCGHSA enrichmentGHSA-hjw9-7f25-8h43 · GitHub severity CRITICAL
  23. 2026-11-06 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  24. 2026-11-05 20:13 UTCEchelonGraph re-scored
  25. 2026-11-05 20:13 UTCGHSA enrichmentGHSA-hjw9-7f25-8h43 · GitHub severity CRITICAL
Show 47 more
  1. 2026-11-05 16:35 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  2. 2026-11-04 19:16 UTCEchelonGraph re-scored
  3. 2026-11-04 19:16 UTCGHSA enrichmentGHSA-hjw9-7f25-8h43 · GitHub severity CRITICAL
  4. 2026-11-04 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  5. 2026-11-03 18:19 UTCEchelonGraph re-scored
  6. 2026-11-03 18:19 UTCGHSA enrichmentGHSA-hjw9-7f25-8h43 · GitHub severity CRITICAL
  7. 2026-11-03 16:44 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  8. 2026-11-03 01:21 UTCEchelonGraph re-scored
  9. 2026-11-03 01:21 UTCGHSA enrichmentGHSA-hjw9-7f25-8h43 · GitHub severity CRITICAL
  10. 2026-11-02 16:42 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  11. 2026-11-02 00:15 UTCEchelonGraph re-scored
  12. 2026-11-02 00:14 UTCGHSA enrichmentGHSA-hjw9-7f25-8h43 · GitHub severity CRITICAL
  13. 2026-11-01 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  14. 2026-10-31 23:17 UTCEchelonGraph re-scored
  15. 2026-10-31 23:17 UTCGHSA enrichmentGHSA-hjw9-7f25-8h43 · GitHub severity CRITICAL
  16. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  17. 2026-10-30 22:21 UTCEchelonGraph re-scored
  18. 2026-10-30 22:21 UTCGHSA enrichmentGHSA-hjw9-7f25-8h43 · GitHub severity CRITICAL
  19. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  20. 2026-10-29 21:23 UTCEchelonGraph re-scored
  21. 2026-10-29 21:23 UTCGHSA enrichmentGHSA-hjw9-7f25-8h43 · GitHub severity CRITICAL
  22. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  23. 2026-10-28 20:26 UTCEchelonGraph re-scored
  24. 2026-10-28 20:26 UTCGHSA enrichmentGHSA-hjw9-7f25-8h43 · GitHub severity CRITICAL
  25. 2026-10-28 20:10 UTCEchelonGraph re-scored
  26. 2026-10-28 20:10 UTCGHSA enrichmentGHSA-hjw9-7f25-8h43 · GitHub severity CRITICAL
  27. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  28. 2026-10-28 14:28 UTCGHSA enrichmentGHSA-hjw9-7f25-8h43 · GitHub severity CRITICAL
  29. 2026-10-28 13:59 UTCEchelonGraph re-scored
  30. 2026-10-28 13:59 UTCGHSA enrichmentGHSA-hjw9-7f25-8h43 · GitHub severity CRITICAL
  31. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  32. 2026-10-27 12:46 UTCGHSA enrichmentGHSA-hjw9-7f25-8h43 · GitHub severity CRITICAL
  33. 2026-10-26 23:10 UTCEchelonGraph re-scored
  34. 2026-10-26 23:09 UTCGHSA enrichmentGHSA-hjw9-7f25-8h43 · GitHub severity CRITICAL
  35. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  36. 2026-10-25 18:48 UTCGHSA enrichmentGHSA-hjw9-7f25-8h43 · GitHub severity CRITICAL
  37. 2026-10-25 16:37 UTCEchelonGraph re-scored
  38. 2026-10-25 16:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  39. 2026-10-24 17:42 UTCEchelonGraph re-scored
  40. 2026-10-24 17:42 UTCGHSA enrichmentGHSA-hjw9-7f25-8h43 · GitHub severity CRITICAL
  41. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  42. 2026-10-23 16:46 UTCEchelonGraph re-scored
  43. 2026-10-23 16:46 UTCGHSA enrichmentGHSA-hjw9-7f25-8h43 · GitHub severity CRITICAL
  44. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  45. 2026-10-23 09:26 UTCEchelonGraph re-scored
  46. 2026-10-23 08:45 UTCEchelonGraph re-scoredFirst assessed: 9.4 CRITICAL
  47. 2026-10-23 08:44 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2025-30047?
CVE-2025-30047 is a critical-severity vulnerability; its CVE record was published on October 23, 2026. CGM CLININET is vulnerable to Remote Code Execution caused by deserialization of untrusted data. The server exposes an HTTP-based API, used by the administrative module, that exchanges data using Java object serialization. An attacker within the same local network is able to send requests to this…
When was the CVE record for CVE-2025-30047 published?
The CVE record for CVE-2025-30047 was published on October 23, 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 28, 2026; the record at its source may have been updated since.
Is CVE-2025-30047 actively exploited?
CVE-2025-30047 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-30047?
CVE-2025-30047 has a CVSS base score of 9.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2025-30047?
The CVE record for CVE-2025-30047 names the fix: "This issue was fixed in version 2026.MS3". The vendor advisories EchelonGraph has for CVE-2025-30047 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-30047

Explore →

Is Your Infrastructure Affected by CVE-2025-30047?

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