# CVE-2025-30047: Remote Code Execution via Java Deserialization in CGM CLININET


- **Severity:** Critical 9.4 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 23 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-hjw9-7f25-8h43

## What is CVE-2025-30047?

CVE-2025-30047 is a critical vulnerability in CGM CLININET, published on 23 Oct 2026. 

### Official description

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

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2025-30047?


## How do I fix CVE-2025-30047?

No fix has been published for CVE-2025-30047 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-30047 being exploited?

There is no known exploitation of CVE-2025-30047 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-30047 and fix it if it is affected.

What it is: CVE-2025-30047 is a critical vulnerability in CGM CLININET, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2025-30047 in the wild and no public exploit code.

Affected product: CGM CLININET. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-30047/ (Markdown: https://insights.sbomify.com/CVE-2025-30047/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-30047
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-30047
- OSV: https://osv.dev/vulnerability/CVE-2025-30047

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-30047/
Summaries are generated and may contain mistakes; the official description above is the record.