CVE-2025-30037: CGM CLININET · Missing Authentication
Affects CGM CLININETSource CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 26 Oct 2026, 11:42 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 27 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| CGM CGM CLININET | Affected
| Fixed in– |
AI-suggested
- Immediate network-level access restrictions: Implement firewall rules or network segmentation to restrict access to the "/int/" endpoints strictly to trusted internal services and IP ranges.
- Deploy an authentication and authorization layer: Ensure that all internal endpoints require strong authentication mechanisms, such as mutual TLS, OAuth tokens, or API keys, to prevent unauthorized access.
- Conduct a thorough security review of the CGM CLININET deployment to identify all exposed internal endpoints and verify their access controls.
- Monitor network traffic and logs for unusual access patterns to the "/int/" endpoints, enabling early detection of exploitation attempts.
- Engage with CGM for official patches or updates addressing this vulnerability and prioritize their deployment once available.
- Implement application-layer gateways or reverse proxies that enforce authentication and restrict access to sensitive endpoints.
- Educate IT and security teams about this vulnerability to ensure rapid response and remediation.
- Consider deploying Web Application Firewalls (WAFs) with custom rules to block unauthorized access to internal paths until patches are applied.
Description
The system exposes several endpoints, typically including "/int/" in their path, that should be restricted to internal services, but are instead publicly accessible without authentication to any host able to reach the application server on port 443/tcp.