Deserialization of Untrusted Data Affecting py3.13-keras package, versions <3.15.0-r0
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-MINIMOSLATEST-PY313KERAS-18598516
- published9 Aug 2026
- disclosed19 Jul 2026
Introduced: 19 Jul 2026
NewCVE-2026-12484 (opens in a new tab)How to fix?
Upgrade Minimos:latest py3.13-keras to version 3.15.0-r0 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream py3.13-keras package and not the py3.13-keras package as distributed by Minimos.
See How to fix? for Minimos:latest relevant fixed versions and status.
A vulnerability in keras-team/keras version 3.15.0 allows unsafe deserialization of attacker-controlled PyTorch pickle data through the public keras.layers.TorchModuleWrapper.from_config method. This method invokes torch.load(..., weights_only=False) without requiring an explicit unsafe opt-in, such as a safe_mode=False parameter. When called outside a SafeModeScope(True) context, the absence of an ambient safe mode state permits unsafe deserialization by default. This issue can lead to arbitrary code execution if untrusted Keras layer configurations are processed using this method. The vulnerability arises because the method does not enforce safe deserialization practices unless explicitly guarded by Keras safe mode.