CVE-2025-48498: Bloomberg Comdb2 · NULL Pointer Dereference
Affects Bloomberg Comdb2Source CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 49% 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:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 22 Jul 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.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Bloomberg Comdb2 | Affected
| Fixed in– |
AI-suggested
1. Network Segmentation: Isolate Bloomberg Comdb2 instances within secure network zones inaccessible from untrusted or public networks to reduce exposure. 2. Access Controls: Implement strict firewall rules to restrict inbound TCP connections to Comdb2 ports only from trusted hosts and management networks. 3. Traffic Monitoring: Deploy deep packet inspection and anomaly detection tools to identify and alert on malformed or suspicious protocol buffer messages targeting Comdb2. 4. Rate Limiting: Apply rate limiting on incoming connections to Comdb2 to mitigate potential denial of service attempts. 5. Incident Response Preparedness: Develop and test response plans for database service disruptions to minimize downtime. 6. Vendor Engagement: Maintain close contact with Bloomberg for timely patch releases and apply updates as soon as they become available. 7. Application Hardening: Where possible, configure Comdb2 to reject unexpected or malformed protocol buffer messages and enable logging for suspicious activity. 8. Redundancy and Failover: Implement high availability and failover mechanisms to reduce impact of potential service outages. These steps go beyond generic advice by focusing on network-level protections, monitoring specific to protocol buffer traffic, and operational readiness.
Description
A null pointer dereference vulnerability exists in the Distributed Transaction component of Bloomberg Comdb2 8.1 when processing a number of fields used for coordination. A specially crafted protocol buffer message can lead to a denial of service. An attacker can simply connect to a database instance over TCP and send the crafted message to trigger this vulnerability.