Keras is vulnerable to Deserialization of Untrusted Data
CVE-2025-9906 · GHSA-36fq-jgmw-4r9c · published 2025-09-19 · updated 2026-05-29
- Severity
- High
- CVSS score
- 7.3
- Chance of exploitation (EPSS)
- 0.20%
- Fixed in
- 3.11.0
- Exploitation No known exploitation
- Automatable No
- Technical impact Total
- CISA SSVC
Keras is vulnerable to Deserialization of Untrusted Data. The source advisory has the full description.
Upgrade keras to 3.11.0 or later.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| keras | PyPI | < 3.11.0 | 3.11.0 |
- CriticalLMDeploy has Remote Code Execution by Pickle Deserialization via handle_zmq_recv in lmdeploy/lmdeploy/pytorch/disagg/conn/engine_conn.pylmdeploy
- CriticalLMdeploy has Remote Code Execution by Pickle Deserialization via zmq_rpc.call_and_response() in InterLM/lmdeploylmdeploy
- CriticalSGLang: Unauthenticated RCE via --enable-custom-logit-processorsglang
- CriticalSGLanG: Multimodal scheduler deserializes untrusted pickle data on 0.0.0.0 ROUTER socketsglang
- Criticaln8n: HTTP Request Node Pagination Prototype Pollution to RCEn8n, n8n, n8n
- Criticaln8n Has an XML Node Prototype Pollution Patch Bypassn8n, n8n, n8n
- CriticalKeras framework vulnerable to deserialization of untrusted datakeras
- CriticalKeras code injection vulnerabilitykeras
- HighKeras: TorchModuleWrapper can deserialize unsafe PyTorch pickle datakeras, keras
- HighKeras: Lambda deserialization can bypass safe mode and execute codekeras, keras
- HighKeras archive extraction utilities allow path traversal and arbitrary file writeskeras
- HighKeras vulnerable to DoS via Malicious .keras Model (HDF5 Shape Bomb Causes Petabyte Allocation in KerasFileEditor)keras, keras