# Open Babel has out-of-bounds write in PQS coord_file parser

Advisory record · `GHSA-f29h-2h58-48r7`

- **Identifiers:** `GHSA-f29h-2h58-48r7` · `CVE-2022-43467` · `PYSEC-2026-2779`
- **State:** Confirmed
- **Severity:** CVSS 9.8 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-119](https://cwe.mitre.org/data/definitions/119.html) · [CWE-787](https://cwe.mitre.org/data/definitions/787.html)
- **Tags:** [Memory corruption](https://agentprime.io/advisories/tag/memory-corruption.md)
- **Published:** 1 Jul 2026
- **Updated:** 13 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 1 Jul 2026, 17:46 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.8: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `openbabel` (PyPI): affected `<3.2.0`; fixed in `3.2.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Open Babel versions before 3.2.0 (the PyPI openbabel package) have an out-of-bounds write in the PQS reader's coord_file parsing path. A user who opens a malicious PQS file with obabel, the OBConversion API, or a language binding could trigger the write, which can be used to attack the affected process. Upgrade to openbabel 3.2.0 or later.

Written 6 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 9.8 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`, from CNA (talos)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0083, the 58th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:02 UTC: First seen by agentprime
- 31 Oct 2026, 15:02 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-f29h-2h58-48r7)

## Sources

- [GitHub Advisory Database: GHSA-f29h-2h58-48r7](https://github.com/advisories/GHSA-f29h-2h58-48r7)
- [OSV: GHSA-f29h-2h58-48r7](https://osv.dev/vulnerability/GHSA-f29h-2h58-48r7)
- <https://github.com/openbabel/openbabel/security/advisories/GHSA-f29h-2h58-48r7>
- <https://nvd.nist.gov/vuln/detail/CVE-2022-43467>
- <https://github.com/openbabel/openbabel/commit/2a7d2cda8bd47daade2e555e34b69651a2e132ef>
- <https://github.com/openbabel/openbabel>
- <https://talosintelligence.com/vulnerability_reports/TALOS-2022-1671>
- <https://www.talosintelligence.com/vulnerability_reports/TALOS-2022-1671>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-f29h-2h58-48r7>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-f29h-2h58-48r7/>. Everything for agents: <https://agentprime.io/llms.txt>.
