CVE-2025-35966: Bloomberg Comdb2 · NULL Pointer Dereference
Affects Bloomberg Comdb2Source CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 26 Oct 2026, 07:57 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-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Bloomberg Comdb2 | Affected
| Fixed in– |
AI-suggested
1. Restrict network access to Bloomberg Comdb2 instances by implementing strict firewall rules and network segmentation to allow only trusted hosts and internal networks to communicate over the Comdb2 TCP port. 2. Monitor network traffic for anomalous or malformed protocol buffer messages targeting the CDB2SQLQUERY protocol, using intrusion detection/prevention systems (IDS/IPS) with custom signatures or behavioral analytics. 3. Apply vendor patches or updates as soon as Bloomberg releases a fix for this vulnerability; maintain close communication with Bloomberg support channels for advisories. 4. If patching is not immediately possible, consider temporarily disabling or restricting external access to Comdb2 services until mitigations are in place. 5. Conduct regular audits of Comdb2 deployment configurations to ensure no unintended exposure to untrusted networks. 6. Implement robust logging and alerting on Comdb2 service crashes or restarts to detect potential exploitation attempts early. 7. Educate network and security teams about this vulnerability to ensure rapid response and containment in case of an incident.
Description
A null pointer dereference vulnerability exists in the CDB2SQLQUERY protocol buffer message handling of Bloomberg Comdb2 8.1. 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.