Miggo at BlackHat 2026!
Easily map the attack path and prioritize which CVEs are a threat to your organization
Miggo AIGenerate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance
Miggo AIRoot Cause AnalysisThe analysis began by examining the provided reference URLs, specifically the GitHub pull request #2862 which was indicated to contain the fix. The commit associated with this pull request, e23a224b8fd9d7c2a7cde9ef4ec6afb4c05aa08a, was then inspected. The commit message and the code changes (diffs) clearly indicated fixes for three distinct vulnerabilities in three different files.
src/math/transform3d.cpp: The patch explicitly adds a bounds check (j < 3) to a while loop within the OpenBabel::transform3d::DescribeAsString function. The commit message confirms this prevents an out-of-bounds read when processing a matrix with an all-zero row, which directly corresponds to the vulnerability description.
src/formats/mol2format.cpp: The patch introduces a nullptr check after a call to mol.GetAtom(aid). The surrounding code and commit message point to the OpenBabel::MOL2Format::ReadMolecule function. This change prevents a crash when processing malformed MOL2 files with invalid atom IDs.
src/formats/xml/cdxmlformat.cpp: Similarly, a nullptr check is added after _pmol->GetAtom(atoms[*vit]) inside the OpenBabel::ChemDrawXMLFormat::EndElement function. This mitigates a NULL pointer dereference when handling malformed CDXML files with invalid atom references.
All three functions were identified as vulnerable because they processed external file formats (CIF, MOL2, CDXML) without sufficient validation, leading to memory safety violations (out-of-bounds read, NULL pointer dereference). The identified functions are the exact locations where the unsafe operations occurred and where the patches were applied.
| Package Name | Ecosystem | Vulnerable Versions | First Patched Version |
|---|---|---|---|
| openbabel | pip | < 3.2.0 | 3.2.0 |
