CVE-2025-10996 json
Open Babel smilesformat.cpp ParseSmiles heap-based overflow
published 2025-09-26 13 mo ago modified 2026-10-19 21 d ago also GHSA-j35x-w4gj-pf7w , PYSEC-2026-2781 , EUVD-2025-31198
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 21%
- public exploits
- 0
- none known
Summary
A vulnerability was detected in Open Babel up to 3.1.1. This issue affects the function OBSmilesParser::ParseSmiles of the file /src/formats/smilesformat.cpp. Performing manipulation results in heap-based buffer overflow. The attack needs to be approached locally. The exploit is now public and may be used.
Patch / fix
- pypi openbabel 3.2.0
- openbabel openSUSE Leap 16.0 3.2.0-bp160.1.1
- openbabel openSUSE Tumbleweed 3.2.0-1.1
opensuse advisories openSUSE-SU-2026:21190-1openSUSE-SU-2026:10936-1
- github.com/openbabel/openbabel@b34cd60 commit
- github.com/openbabel/openbabel#2913 pull request
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-10996 updated cvss 5.3
openbabel: Open Babel smilesformat.cpp ParseSmiles heap-based overflow
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 13 mo ago
Exploit prediction
0.29% chance of exploitation in the next 30 days, higher than 21% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/user-attachments/files/22318556/poc.zip referenced PoC, tagged "exploit" by a source, unverified
- github.com https://github.com/openbabel/openbabel/issues/2831 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 4.8 | CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P |
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R |
| CNA | 3.0 | 5.3 | CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R |
| CNA | 2.0 | 4.3 | AV:L/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:UR |
| CNA | 4.0 | 1.9 | CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L |
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| CNA | 2.0 | 4.3 | AV:L/AC:L/Au:S/C:P/I:P/A:P |
| OSV | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | openbabel | <3.2.0 |
3.2.0 |
Affected products
- n/a Open Babel
Classification
References
-
github.com
/openbabel/openbabel/pull/2913
web
-
github.com
/openbabel/openbabel/commit/b34cd604
web
-
github.com
/user-attachments/files/22318556/poc.zip
exploit, web
-
github.com
/openbabel/openbabel/issues/2831
issue-tracking, web, exploit
-
vuldb.com
/?id.325924
vdb-entry, technical-description, web, third-party-advisory
-
vuldb.com
/?ctiid.325924
signature, permissions-required, web, vdb-entry
-
vuldb.com
/?submit.654060
third-party-advisory, web, vdb-entry
-
github.com
/openbabel/openbabel/security/advisories/GHSA-j35x-w4gj-pf7w
web
-
nvd.nist.gov
/vuln/detail/CVE-2025-10996
advisory
-
github.com
/openbabel/openbabel
package
-
pypi.org
/project/openbabel
package
-
github.com
/advisories/GHSA-j35x-w4gj-pf7w
advisory
Sources
- CVE List CVE-2025-10996
- GitHub Advisory GHSA-j35x-w4gj-pf7w
- NVD CVE-2025-10996
- OSV PYSEC-2026-2781
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.