- Veröffentlicht
- 29.10.2025 09:48
- Zuletzt geändert
- 10.09.2026
- EPSS (30 Tage)
- 0.3 %
- CVSS-Vektor
- CVSS:4.0/AV:A/AC:H/AT:P/PR:L/UI:P/VC:H/VI:L/VA:L/SC:H/SI:L/SA:L
Beschreibung
Originaltext der Quelle, nicht übersetzt.
The Keras.Model.load_model method, including when executed with the intended security mitigation safe_mode=True, is vulnerable to arbitrary local file loading and Server-Side Request Forgery (SSRF).
This vulnerability stems from the way the StringLookup layer is handled during model loading from a specially crafted .keras archive. The constructor for the StringLookup layer accepts a vocabulary argument that can specify a local file path or a remote file path.
* Arbitrary Local File Read: An attacker can create a malicious .keras file that embeds a local path in the StringLookup layer's configuration. When the model is loaded, Keras will attempt to read the content of the specified local file and incorporate it into the model state (e.g., retrievable via get_vocabulary()), allowing an attacker to read arbitrary local files on the hosting system.
* Server-Side Request Forgery (SSRF): Keras utilizes tf.io.gfile for file operations. Since tf.io.gfile supports remote filesystem handlers (such as GCS and HDFS) and HTTP/HTTPS protocols, the same mechanism can be leveraged to fetch content from arbitrary network endpoints on the server's behalf, resulting in an SSRF condition.
The security issue is that the feature allowing external path loading was not properly restricted by the safe_mode=True flag, which was intended to prevent such unintended data access.
Status beim Hersteller
Red Hat stuft seine Produktlinien ein: 2 betroffen.
Red Hat OpenShift AI (RHOAI)
BetroffenFix zurückgestellt
rhoai/odh-kserve-agent-rhel9, rhoai/odh-kserve-controller-rhel9, rhoai/odh-kserve-router-rhel9, rhoai/odh-kserve-storage-initializer-rhel9, rhoai/odh-modelmesh-runtime-adapter-rhel8, rhoai/odh-modelmesh-runtime-adapter-rhel9, rhoai/odh-pipeline-runtime-tensorflow-cuda-py312-rhel9, rhoai/odh-pipeline-runtime-tensorflow-rocm-py312-rhel9, rhoai/odh-workbench-jupyter-tensorflow-cuda-py312-rhel9, rhoai/odh-workbench-jupyter-tensorflow-rocm-py312-rhel9
Red Hat Trusted Artifact Signer
BetroffenFix zurückgestellt
rhtas/model-transparency-rhel9
Weitere betroffene Pakete (9)
Azure Linux:2keraskein Fix bekanntAZL-69583
Azure Linux:3keraskein Fix bekanntAZL-69021
CVEKeras/Keras3.12.0CVE-2025-12058
Debian:11keraskein Fix bekanntDEBIAN-CVE-2025-12058
PyPIkeras3.12.0GHSA-mq84-hjqx-cwf2
PyPIkeras3.12.0PYSEC-2026-1487
TuxCare:PyPIkeras2.15.0.post0 → 2.15.0.post5+tuxcareCLSA-2026-1794298440
Ubuntu:18.04:LTSkeraskein Fix bekanntUBUNTU-CVE-2025-12058
Ubuntu:20.04:LTSkeraskein Fix bekanntUBUNTU-CVE-2025-12058
Empfohlene Prüfung
- Feststellen, ob und in welcher Version die betroffenen Pakete in Ihren Systemen, Images und Abhängigkeiten vorkommen.
- Wo eine Fix-Version genannt ist: aktualisieren. Wo nicht: Hersteller-Advisory und Referenzen auf Workarounds prüfen.
- Erreichbarkeit beachten: Der Angriffsweg (Nachbarnetz · Nutzerinteraktion) ist aus dem CVSS-Vektor abgeleitet.
Diese Seite sagt nichts darüber, ob Ihre Systeme betroffen sind. Das klärt erst eine Prüfung Ihrer Versionen.
Referenzen
- github.com/keras-team/keras/security/advisories/GHSA-qg93-c7p6-gg7f
- github.com/keras-team/keras/pull/21751
- nvd.nist.gov/vuln/detail/CVE-2025-12058
- security-tracker.debian.org/tracker/CVE-2025-12058
- github.com/keras-team/keras/commit/61ac8c1e51862c471dee7b49029c356f55531487
- github.com/keras-team/keras
- www.cve.org/CVERecord
- pypi.org/project/keras
- github.com/advisories/GHSA-mq84-hjqx-cwf2
- ubuntu.com/security/CVE-2025-12058
- security.access.redhat.com/data/csaf/v2/vex/2025/cve-2025-12058.json
- access.redhat.com/security/cve/CVE-2025-12058
- bugzilla.redhat.com/show_bug.cgi