openbabel

CVE-2022-46290

CVE-2022-46290 is a high-severity out-of-bounds write vulnerability in openbabel (pip), affecting versions < 3.2.0. It is fixed in 3.2.0.

Key facts
CVSS score
7.8
High
Attack vector
Local
Issuing authority
GitHub Advisory Database
Affected package
openbabel
Fixed in
3.2.0
Disclosed
2022

Summary

Summary A memory-safety vulnerability in Open Babel's ORCA parser allowed an out-of-bounds write when reading a crafted input file. Details A second variant of the nAtoms out-of-bounds write in the ORCA reader: a different malformed-input path produced the same class of write past the end of the destination buffer. 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 ORCA file with the obabel tool, the OBConversion API, or any of the language bindings (Python, Ruby, Java, R, Perl, C#, PHP). 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/b239d06e A minimized reproducer for this CVE is checked in under test/files/fuzz_regress/ and is exercised on every CI build under ASAN+UBSAN by the fuzzregresstest harness. Credit Reported by Cisco TALOS.

Impact

What is out-of-bounds write?

A write operation targets a memory location beyond the intended buffer boundary. Typical impact: memory corruption, crash, or arbitrary code execution.

Severity and exposure

CVE-2022-46290 has a CVSS score of 7.8 (High). The vector is requires local access, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.

A fixed version is available (3.2.0). Upgrading removes the vulnerable code path.

Affected versions

pip

  • openbabel (< 3.2.0)

Security releases

  • openbabel → 3.2.0 (pip)
Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.

Kodem's runtime-powered SCA identifies whether CVE-2022-46290 is reachable in your applications. Explore open-source security for your team.

See if CVE-2022-46290 is reachable in your applications. Get a demo

Already deployed Kodem? See CVE-2022-46290 in your environment

Remediation advice

Upgrade openbabel to 3.2.0 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently asked questions about CVE-2022-46290

What is CVE-2022-46290?

CVE-2022-46290 is a high-severity out-of-bounds write vulnerability in openbabel (pip), affecting versions < 3.2.0. It is fixed in 3.2.0. A write operation targets a memory location beyond the intended buffer boundary.

How severe is CVE-2022-46290?

CVE-2022-46290 has a CVSS score of 7.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of openbabel are affected by CVE-2022-46290?

openbabel (pip) versions < 3.2.0 is affected.

Is there a fix for CVE-2022-46290?

Yes. CVE-2022-46290 is fixed in 3.2.0. Upgrade to this version or later.

Is CVE-2022-46290 exploitable, and should I be worried?

Whether CVE-2022-46290 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo

What actually determines whether CVE-2022-46290 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2022-46290?

Upgrade openbabel to 3.2.0 or later.

Stop the waste.
Protect your environment with Kodem.