Keras up to 3.11.2 Model Archive File Model.load_model dynamically-managed code resources
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.0 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as problematic has been discovered in Keras up to 3.11.2. This impacts the function Model.load_model of the component Model Archive File Handler. Such manipulation leads to dynamically-managed code resources.
This vulnerability is traded as CVE-2025-9905. The attack may be launched remotely. There is no exploit available.
Details
A vulnerability was found in Keras up to 3.11.2 and classified as problematic. Affected by this issue is the function Model.load_model of the component Model Archive File Handler. The manipulation with an unknown input leads to a dynamically-managed code resources vulnerability. Using CWE to declare the problem leads to CWE-913. The product does not properly restrict reading from or writing to dynamically-managed code resources such as variables, objects, classes, attributes, functions, or executable instructions or statements. Impacted is confidentiality, integrity, and availability. CVE summarizes:
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 .h5/.hdf5 model archive that, when loaded via Model.load_model, will trigger arbitrary code to be executed. This is achieved by crafting a special .h5 archive file that uses the Lambda layer feature of keras which allows arbitrary Python code in the form of pickled code. The vulnerability comes from the fact that the safe_mode=True option is not honored when reading .h5 archives. Note that the .h5/.hdf5 format is a legacy format supported by Keras 3 for backwards compatibility.
The weakness was shared by Gabriele Digregorio. The advisory is shared for download at github.com. This vulnerability is handled as CVE-2025-9905 since 09/03/2025. The exploitation is known to be difficult. The attack may be launched remotely. No form of authentication is required for exploitation. Successful exploitation requires user interaction by the victim. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 09/28/2025).
The vulnerability scanner Nessus provides a plugin with the ID 265855 (Linux Distros Unpatched Vulnerability : CVE-2025-9905), which helps to determine the existence of the flaw in a target environment.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at Tenable (265855) and EUVD (EUVD-2025-30277). Once again VulDB remains the best source for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 5.0VulDB Meta Temp Score: 5.0
VulDB Base Score: 5.0
VulDB Temp Score: 5.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Dynamically-managed code resourcesCWE: CWE-913
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 265855
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2025-9905
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
09/03/2025 CVE reserved09/19/2025 Advisory disclosed
09/19/2025 VulDB entry created
09/28/2025 VulDB entry last update
Sources
Advisory: github.comResearcher: Gabriele Digregorio
Status: Confirmed
CVE: CVE-2025-9905 (🔒)
GCVE (CVE): GCVE-0-2025-9905
GCVE (VulDB): GCVE-100-325004
EUVD: 🔒
Entry
Created: 09/19/2025 10:32Updated: 09/28/2025 21:40
Changes: 09/19/2025 10:32 (65), 09/20/2025 18:09 (1), 09/28/2025 21:40 (2)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.