comdb2 vulnerabilities and fixes
Recent CVEs affecting comdb2, with upgrade or downgrade steps. 5 tracked.
comdb2 has 5 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2025-07-22. Highest priority: CVE-2025-46354 (score 51/100).
- CVE-2025-48498 HIGH 7.5 DOWNGRADE A null pointer dereference vulnerability exists in the Distributed Transaction component of Bloomberg Comdb2 8
- CVE-2025-46354 HIGH 7.5 DOWNGRADE A denial of service vulnerability exists in the Distributed Transaction Commit/Abort Operation functionality o
- CVE-2025-36520 HIGH 7.5 DOWNGRADE A null pointer dereference vulnerability exists in the net_connectmsg Protocol Buffer Message functionality of
- CVE-2025-36512 HIGH 7.5 DOWNGRADE A denial of service vulnerability exists in the Bloomberg Comdb2 8.1 database when handling a distributed tran
- CVE-2025-35966 HIGH 7.5 DOWNGRADE A null pointer dereference vulnerability exists in the CDB2SQLQUERY protocol buffer message handling of Bloomb
FAQ
How do I fix comdb2 vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is comdb2 being exploited right now?
None of the tracked comdb2 CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which comdb2 CVE should I patch first?
CVE-2025-46354 currently ranks highest (51/100): A denial of service vulnerability exists in the Distributed Transaction Commit/Abort Operation functionality o.