Safe Mode Bypass in keras-team/keras
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| keras-team | keras-team/keras | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Keras | Keras |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-4f3f-g24h-fr8m | Keras has an untrusted deserialization vulnerability |
No CVSS v4.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.420% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Keras
Keras keras |
|
| Vendors & Products |
Keras
Keras keras |
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A vulnerability in the `TFSMLayer` class of the `keras` package, version 3.13.0, allows attacker-controlled TensorFlow SavedModels to be loaded during deserialization of `.keras` models, even when `safe_mode=True`. This bypasses the security guarantees of `safe_mode` and enables arbitrary attacker-controlled code execution during model inference under the victim's privileges. The issue arises due to the unconditional loading of external SavedModels, serialization of attacker-controlled file paths, and the lack of validation in the `from_config()` method. | |
| Title | Safe Mode Bypass in keras-team/keras | |
| Weaknesses | CWE-502 | |
| References |
| |
| Metrics |
cvssV3_0
|