Keras
AI Threat Alert tracks 7 known AI/ML vulnerabilities affecting Keras products — each enriched with CVSS severity, EPSS exploit probability, patch status, and CISO-grade analysis. Browse every Keras CVE below, sorted by severity and recency.
| Severity | CVE | Headline | Package | CVSS |
|---|---|---|---|---|
| CRITICAL | CVE-2024-3660 | Keras: RCE via malicious model deserialization | keras | 9.8 |
| MEDIUM | CVE-2024-55459 | Keras: path traversal enables arbitrary file write | keras | 6.5 |
| CRITICAL | CVE-2025-1550 | Keras: safe_mode bypass enables RCE via model loading | keras | 9.8 |
| HIGH | CVE-2025-8747 | Keras: safe mode bypass enables RCE via model load | keras | 7.8 |
| HIGH | CVE-2025-9905 | Keras: safe_mode bypass enables RCE via .h5 model files | keras | 7.3 |
| HIGH | CVE-2025-9906 | Keras: safe_mode bypass enables RCE via model load | keras | 7.3 |
| HIGH | CVE-2026-1669 | keras: File Control enables path manipulation | keras | 7.5 |
Frequently asked questions
How many known vulnerabilities affect Keras?
7 AI/ML CVEs affecting Keras products are tracked, sourced from NVD and GitHub Advisory.
What Keras products are affected?
The CVEs below map to the Keras AI/ML packages and tools tracked by AI Threat Alert; open any CVE to see the affected components and versions.
Where does the Keras vulnerability data come from?
Data is sourced from NVD and GitHub Advisory, then enriched with CVSS severity, EPSS exploit probability, and patch status for each CVE.
How can I monitor Keras for new vulnerabilities?
AI Threat Alert tracks Keras continuously; a Pro subscription adds breaking alerts when new CVEs affecting Keras are published.
How do I assess Keras's security exposure?
Each CVE below carries CVSS severity and exploitation signals, so you can review the highest-severity Keras issues first and judge the exposure for your stack.