Quick answers
- Is CVE-2026-2705 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-2705 being exploited in the wild.
- How severe is CVE-2026-2705?
- Medium severity, with a CVSS score of 5.5, published 30 June 2026.
- Which products and versions are affected?
- openbabel (PyPI) < 3.2.0, ECOSYSTEM:introduced=0,fixed=3.2.0.
- Is there a fix for CVE-2026-2705?
- Yes. openbabel (PyPI): upgrade to 3.2.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-2705 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-2705?
- Check whether you run openbabel (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- openbabel (PyPI): upgrade to 3.2.0 or later
pip install "openbabel>=3.2.0"
Technical details
A memory-safety vulnerability exists in Open Babel's MOL2 file format parser due to a NULL pointer dereference in the `OBAtom::SetFormalCharge` function. The flaw is triggered when the parser encounters a malformed atom record in a MOL2 file, causing it to call the method on a NULL atom pointer. An attacker can exploit this by providing a crafted MOL2 file to the `obabel` CLI tool, the `OBConversion` API, or any of its language bindings (Python, Java, etc.). This results in a denial-of-service (application crash). The issue is fixed in version 3.2.0.
Affected products
- Open Babel openbabel <= 3.1.1
Identifiers
- CVE-2026-2705
- GHSA-4w5w-4fhm-q483
- PYSEC-2026-2770
Timeline
- 2026-05-26: patched: Version 3.2.0 released
- 2026-06-30: advisory: GitHub Advisory published