GHSA-6XW4-2G22-26H8

Vulnerability from github – Published: 2026-06-30 18:46 – Updated: 2026-06-30 18:46
VLAI
Summary
Open Babel has an out-of-bounds read in CIF transform3d::DescribeAsString
Details

Summary

A memory-safety vulnerability in Open Babel's CIF file format parser allowed an out-of-bounds read when reading a crafted input file.

Details

The flaw was in OpenBabel::transform3d::DescribeAsString. A malformed symmetry-operation string caused the parser to read past the end of its internal buffer while formatting the description.

Impact

Open Babel is a C++ library and CLI used to read and write chemistry file formats; it is shipped by Linux distributions and embedded in services that may parse untrusted input. Triggering this vulnerability requires the victim to open a malicious CIF file with the obabel tool, the OBConversion API, or any of the language bindings.

Affected versions

All releases up to and including 3.1.1.

Patched version

3.2.0 (released 2026-05-26).

Patch

Fix commit: https://github.com/openbabel/openbabel/commit/e23a224b Tracked in #2862.

A minimized reproducer for this CVE is checked in at test/files/fuzz_regress/cve-2026-2704.cif and is exercised on every CI build under ASAN+UBSAN by the fuzzregresstest harness.

Credit

Reported by Vedant Madane (@VedantMadane).

Severity
4.4 (Medium)
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:L
2.1 (Low)
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P
Show details on source website
To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "openbabel"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "3.2.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-2704"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-119",
      "CWE-125"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-06-30T18:46:12Z",
    "nvd_published_at": null,
    "severity": "LOW"
  },
  "details": "\u003e ### Summary\n\u003e\n\u003e A memory-safety vulnerability in Open Babel\u0027s CIF file format parser\n\u003e allowed an out-of-bounds read when reading a crafted input file.\n\u003e\n\u003e ### Details\n\u003e\n\u003e The flaw was in `OpenBabel::transform3d::DescribeAsString`. A malformed\n\u003e symmetry-operation string caused the parser to read past the end of its\n\u003e internal buffer while formatting the description.\n\u003e\n\u003e ### Impact\n\u003e\n\u003e Open Babel is a C++ library and CLI used to read and write chemistry\n\u003e file formats; it is shipped by Linux distributions and embedded in\n\u003e services that may parse untrusted input. Triggering this vulnerability\n\u003e requires the victim to open a malicious CIF file with the `obabel`\n\u003e tool, the OBConversion API, or any of the language bindings.\n\u003e\n\u003e ### Affected versions\n\u003e\n\u003e All releases up to and including 3.1.1.\n\u003e\n\u003e ### Patched version\n\u003e\n\u003e 3.2.0 (released 2026-05-26).\n\u003e\n\u003e ### Patch\n\u003e\n\u003e Fix commit: https://github.com/openbabel/openbabel/commit/e23a224b\n\u003e Tracked in #2862.\n\u003e\n\u003e A minimized reproducer for this CVE is checked in at\n\u003e `test/files/fuzz_regress/cve-2026-2704.cif` and is exercised on every\n\u003e CI build under ASAN+UBSAN by the `fuzzregresstest` harness.\n\u003e\n\u003e ### Credit\n\u003e\n\u003e Reported by Vedant Madane (@VedantMadane).",
  "id": "GHSA-6xw4-2g22-26h8",
  "modified": "2026-06-30T18:46:12Z",
  "published": "2026-06-30T18:46:12Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/openbabel/openbabel/security/advisories/GHSA-6xw4-2g22-26h8"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-2704"
    },
    {
      "type": "WEB",
      "url": "https://github.com/openbabel/openbabel/issues/2848"
    },
    {
      "type": "WEB",
      "url": "https://github.com/openbabel/openbabel/pull/2862"
    },
    {
      "type": "WEB",
      "url": "https://github.com/VedantMadane/openbabel/commit/e23a224b8fd9d7c2a7cde9ef4ec6afb4c05aa08a"
    },
    {
      "type": "WEB",
      "url": "https://github.com/oneafter/0128/blob/main/ob1/repro.cif"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/openbabel/openbabel"
    },
    {
      "type": "WEB",
      "url": "https://github.com/openbabel/openbabel/releases/tag/openbabel-3-2-0"
    },
    {
      "type": "WEB",
      "url": "https://vuldb.com/?ctiid.346650"
    },
    {
      "type": "WEB",
      "url": "https://vuldb.com/?id.346650"
    },
    {
      "type": "WEB",
      "url": "https://vuldb.com/?submit.754378"
    },
    {
      "type": "WEB",
      "url": "https://vuldb.com/submit/754378"
    },
    {
      "type": "WEB",
      "url": "https://vuldb.com/vuln/346650"
    },
    {
      "type": "WEB",
      "url": "https://vuldb.com/vuln/346650/cti"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:L",
      "type": "CVSS_V3"
    },
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P",
      "type": "CVSS_V4"
    }
  ],
  "summary": "Open Babel has an out-of-bounds read in CIF transform3d::DescribeAsString"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Loading timeline…




    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.