Vulnérabilités / openSUSE-SU-2026:21190-1

critique

openSUSE-SU-2026:21190-1

Security update for openbabel

Dans la Trivy database depuis au moins le 24 oct. 2026, 07:11 UTCLa date d'entrée avant ce build n'est pas enregistrée.

Sévérité par source

Aucune source ne donne de score CVSS.

Le label propre à Trivy est CRITICAL. Critique selon SUSE.

Description

This update for openbabel fixes the following issues: Changes in openbabel: - Update to version 3.2.0: * Add an L-BFGS optimizer, used by default for gen3d and conformer searches * New macrocycle ring builder (Dale codes) for better initial 3D geometry of large rings * Add KET (Ketcher JSON) and ChemicalJSON (.cjson) format support * Drop Python 2 support; Python 3.13 supported * Faster, vectorized distance-geometry implementation * Full CMake 4 compatibility and modernized build * Backwards compatible with 3.0 and 3.1 * Fix many crash and memory-safety bugs found via OSS-Fuzz and TALOS, including the following security issues: CVE-2022-37331 (boo#1217676), CVE-2022-41793, CVE-2022-42885, CVE-2022-43467, CVE-2022-43607, CVE-2022-44451, CVE-2022-46280, CVE-2022-46289, CVE-2022-46290, CVE-2022-46291, CVE-2022-46292, CVE-2022-46294, CVE-2022-46295, CVE-2025-10994, CVE-2025-10995, CVE-2025-10996, CVE-2025-10997, CVE-2025-10998, CVE-2025-10999, CVE-2025-11000, CVE-2026-2704 (boo#1258501), CVE-2026-2705 (boo#1258507) and CVE-2026-3408 (boo#1259041)

Paquets affectés et versions corrigées

SourcePaquetCorrigé en
openSUSE Leap 16.0libopenbabel8, openbabel, openbabel-devel et 2 autres3.2.0-bp160.1.1
Afficher les 5 entrées d'une source
SourcePaquetCorrigé en
openSUSE Leap 16.0libopenbabel83.2.0-bp160.1.1
openSUSE Leap 16.0openbabel3.2.0-bp160.1.1
openSUSE Leap 16.0openbabel-devel3.2.0-bp160.1.1
openSUSE Leap 16.0openbabel-gui3.2.0-bp160.1.1
openSUSE Leap 16.0python3-openbabel3.2.0-bp160.1.1

Références

Les 28 références

Vulnerability data compiled from the Trivy vulnerability database (trivy-db, Aqua Security, Apache License 2.0), which aggregates third-party advisories. CVE records are published by The MITRE Corporation under the CVE Terms of Use; CVE is a trademark of MITRE. This product uses data from the NVD API but is not endorsed or certified by the NVD. Severity, titles and advisory data from the GitHub Advisory Database (CC BY 4.0), Red Hat security data (CC BY 4.0) and the other sources linked on each entry. Entries may be summarised or re-formatted; the linked original is the authoritative record.