CVE-2025-48981VulnerabilityPublished 8 Oct 2025Updated 9 Oct 2025

CVE-2025-48981: CompuGroup Medical CGM MEDICO · Vulnerability

Affects CompuGroup Medical CGM MEDICOSource CVE Database V5

Not known to be exploited · CVSS 8.6 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

8.6High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 8 Oct 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 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
CompuGroup Medical CGM MEDICO	Affected =29.0	Fixed in–

AI-suggested

To mitigate CVE-2025-48981, organizations should immediately enforce encryption on all DNET protocol communications within CGM MEDICO, either by configuring the software to require encryption or by deploying network-level encryption solutions such as IPsec tunnels within the intranet. Network segmentation should be implemented to isolate CGM MEDICO systems from general user networks, limiting access to trusted devices and personnel only. Continuous monitoring of internal network traffic for unusual patterns or unauthorized access attempts is critical to detect exploitation attempts early. Organizations should also conduct internal audits to identify all CGM MEDICO installations and verify their version and configuration status. Until a vendor patch is available, consider deploying host-based intrusion detection systems (HIDS) on CGM MEDICO servers to alert on suspicious activities. Employee training on insider threat awareness and strict access controls can further reduce risk. Finally, maintain up-to-date backups of medical data to ensure recovery in case of data integrity compromise.

Description

CVE-2025-48981 is a high-severity vulnerability in CompuGroup Medical's CGM MEDICO product version 29.0. It stems from an insecure implementation of the proprietary DNET protocol, where encryption is optional, allowing attackers on the same intranet to eavesdrop and manipulate transmitted data. This vulnerability can lead to significant confidentiality breaches and limited integrity and availability impacts. Exploitation requires network access but no authentication or user interaction. Although no known exploits are currently in the wild, the vulnerability poses a substantial risk to healthcare organizations relying on CGM MEDICO. European healthcare providers using this software are particularly at risk due to the sensitive nature of medical data and the widespread use of CGM MEDICO in Europe. Mitigation involves enforcing encryption on DNET communications, network segmentation, and monitoring internal traffic for anomalies. Countries with large healthcare sectors using CGM MEDICO, such as Germany, France, and the UK, are most likely to be affected. Given the CVSS score of 8.

Impact

For European organizations, particularly healthcare providers using CGM MEDICO, this vulnerability poses a serious threat to patient data confidentiality and the integrity of medical records. Unauthorized eavesdropping can lead to exposure of sensitive personal health information, violating GDPR and other data protection regulations, potentially resulting in legal and financial consequences. Manipulation of data could cause incorrect medical decisions, risking patient safety and undermining trust in healthcare systems. The vulnerability's exploitation within intranet environments means that insider threats or lateral movement by attackers who breach perimeter defenses could leverage this flaw. Given the critical nature of healthcare infrastructure in Europe and the reliance on CGM MEDICO in multiple countries, the impact could be widespread, affecting hospital operations and patient care continuity. Additionally, the potential for data manipulation, even if limited, could disrupt clinical workflows and damage organizational reputation.

Summary

CVE-2025-48981 identifies a critical vulnerability in CompuGroup Medical's CGM MEDICO software, specifically version 29.0. The root cause is an insecure implementation of the proprietary DNET protocol, which is used for communication within the product. The protocol allows encryption to be optional, and in many cases, it is not enforced, enabling attackers with access to the same intranet to intercept (eavesdrop) and manipulate data transmitted over this protocol. This vulnerability falls under CWE-311 (Missing Encryption of Sensitive Data), indicating a failure to adequately protect data in transit. The attack vector is network-based (AV:N), requiring no privileges (PR:N) or user interaction (UI:N), making it relatively easy to exploit if an attacker gains intranet access. The impact is primarily on confidentiality (high), with some impact on integrity and availability (both low). Although no exploits have been reported in the wild yet, the vulnerability's characteristics make it a significant risk, especially in healthcare environments where CGM MEDICO is deployed. The lack of encryption can expose sensitive patient data and allow attackers to alter medical information, potentially leading to incorrect treatments or diagnoses. The vulnerability was published on October 8, 2025, and has a CVSS v3.1 score of 8.6, categorizing it as high severity. No patches or fixes have been linked yet, emphasizing the need for immediate mitigation strategies.

CWE-311Missing Encryption of Sensitive Data (opens in a new tab)
Class weaknessLikelihood of exploit: HighOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product does not encrypt sensitive or critical information before storage or transmission.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Requirements
Clearly specify which data or resources are valuable enough that they should be protected by encryption. Require that any transmission or storage of this data/resource should use well-vetted encryption algorithms.
Architecture and Design
Ensure that encryption is properly integrated into the system design, including but not necessarily limited to: Encryption that is needed to store or transmit private data of the users of the system; Encryption that is needed to protect the system itself from unauthorized disclosure or tampering
Architecture and Design · Libraries or Frameworks
When there is a need to store or transmit sensitive data, use strong, up-to-date cryptographic algorithms to encrypt that data. Select a well-vetted algorithm that is currently considered to be strong by experts in the field, and use well-tested implementations.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
User Privacy Protection (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V6.1.3 (opens in a new tab)
V6.1.2 (opens in a new tab)
V6.1.1 (opens in a new tab)
Attack patterns
Sniffing Attacks (opens in a new tab)
Sniffing Network Traffic (opens in a new tab)
Lifting Sensitive Data Embedded in Cache (opens in a new tab)
Accessing/Intercepting/Modifying HTTP Cookies (opens in a new tab)
Retrieve Embedded Sensitive Data (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

cgm.com/deu_de/allgemein/cybersecurity-en/security-advisoriy.html (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 16 Oct 2025, 01:19 UTC

WeaknessesCWE-311

Technical details

References

Community reviews

Related threats