CVE-2025-49655 is a critical deserialization vulnerability in Keras affecting versions 3.11.0 through 3.11.2 (fixed in 3.11.3). The flaw exists in the model loading/deserialization path for .keras archives, specifically when deserializing TorchModuleWrapper objects. A malicious actor can craft a .keras model archive with a manipulated config.json that defines a TorchModuleWrapper layer with malicious initialization parameters. During model load, Keras instantiates the TorchModuleWrapper object and the underlying PyTorch module without sufficient validation of deserialized parameters. This unsafe deserialization path remains reachable even when Keras safe mode is enabled, allowing arbitrary code execution from both locally supplied and remotely obtained model files.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A critical remote code execution vulnerability in Keras 3 that allows code execution when a model is loaded.
A critical deserialization-of-untrusted-data issue in Keras (3.11.0 to <3.11.3) where loading a malicious Keras file containing a TorchModuleWrapper can lead to arbitrary code execution even when safe mode is enabled; triggerable via local or remote files.
A deserialization vulnerability in Keras that allows arbitrary code execution during loading of malicious .keras model files via TorchModuleWrapper, even when safe mode is enabled.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.