The Keras Model.load_model method can be exploited to achieve arbitrary code execution, even with safe_mode=True.
One can create a specially crafted .keras model archive that, when loaded via Model.load_model, will trigger arbitrary code to be executed. This is achieved by crafting a special config.json (a file within the .keras archive) that will invoke keras.config.enable_unsafe_deserialization() to disable safe mode. Once safe mode is disable, one can use the Lambda layer feature of keras, which allows arbitrary Python code in the form of pickled code. Both can appear in the same archive. Simply the keras.config.enable_unsafe_deserialization() needs to appear first in the archive and the Lambda with arbitrary code needs to be second.
Metrics
Affected Vendors & Products
References
| Link | Providers |
|---|---|
| https://github.com/keras-team/keras/pull/21429 |
|
History
Fri, 19 Sep 2025 12:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Fri, 19 Sep 2025 08:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The Keras Model.load_model method can be exploited to achieve arbitrary code execution, even with safe_mode=True. One can create a specially crafted .keras model archive that, when loaded via Model.load_model, will trigger arbitrary code to be executed. This is achieved by crafting a special config.json (a file within the .keras archive) that will invoke keras.config.enable_unsafe_deserialization() to disable safe mode. Once safe mode is disable, one can use the Lambda layer feature of keras, which allows arbitrary Python code in the form of pickled code. Both can appear in the same archive. Simply the keras.config.enable_unsafe_deserialization() needs to appear first in the archive and the Lambda with arbitrary code needs to be second. | |
| Title | Arbitrary Code execution in Keras Safe Mode | |
| Weaknesses | CWE-502 | |
| References |
| |
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: Google
Published: 2025-09-19T08:15:04.349Z
Updated: 2025-09-19T11:51:44.222Z
Reserved: 2025-09-03T07:27:23.895Z
Link: CVE-2025-9906
Updated: 2025-09-19T11:51:40.833Z
Status : Received
Published: 2025-09-19T09:15:36.353
Modified: 2025-09-19T09:15:36.353
Link: CVE-2025-9906
No data.