NVD / CVE Program· CNA Google

CVE-2025-8747: Keras safe_mode bypass allows arbitrary code execution when loading a malicious model.

Noroxi assessment

Priority: Monitor (action score 34/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.11% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. No special conditions are required; it is repeatable.
Fixed version: azl3 keras 3.3.3-2 on Azure Linux 3.0 3.3.3-3.

Low priority for now. Upgrade to azl3 keras 3.3.3-2 on Azure Linux 3.0 3.3.3-3 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

A safe mode bypass vulnerability in the `Model.load_model` method in Keras versions 3.0.0 through 3.10.0 allows an attacker to achieve arbitrary code execution by convincing a user to load a specially crafted `.keras` model archive.

HighCVSS 8.6 · v4.0—No exploit Fix available

Published: Aug 11, 2025
Updated: Jun 17, 2026
EPSS: 0.1% · 1th percentile
CWE: CWE-502

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 34 / 40 · 8.6 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.1%

CISA SSVC decision

Exploitation: proof of concept
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · Google: 8.6; NVD has not scored this yet; the score shown is the CNA’s.

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/AU:Y/R:A

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
keras	keras	cpe:2.3:a:keras:keras

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

keras keras3.0.0 and later · up to 3.10.0 inclusive

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Google). Independent of NVD's CPE analysis and usually ahead of it.

Google Keras
- 3.0.0 and later · up to and including 3.10.0affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
PyPI	keras	from 3.0.0 · before 3.11.0	3.11.0
PyPI	keras	all versions	—

Same product

keras: all records

Other highest-scoring records for the same primary product.

CVE-2024-3660Arbitrary code injection vulnerability in Keras framework < 2.13
40Plan
CVE-2026-12481Deserialization of Untrusted Data in keras-team/keras
39Monitor
CVE-2025-49655Deserialization of untrusted data can occur in versions of the Keras framework running versions 3.11.0 up to but not including 3.11.3, enabl
39Monitor

Published before and after this one in the same product

← EarlierCVE-2024-55459Jan 8, 2025 · An issue in keras 3.7.0 allows attackers to write arbitrary files to the user's machine via downloading a crafted tar file through the get_f
26Monitor
← EarlierCVE-2025-1550Mar 11, 2025 · Arbitrary Code Execution via Crafted Keras Config for Model Loading
30Monitor
Later →CVE-2025-9905Sep 19, 2025 · Arbitary Code execution in Keras load_model()
29Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
azl3 keras 3.3.3-2 on Azure Linux 3.0	3.3.3-3 · CBL-Mariner Releases	Microsoft (MSRC)
PyPI:keras	3.11.0	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

keras-team/kerasPR 21429

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

JFrog Security Research Teamreporter

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2025-4965567 days apartDeserialization of untrusted data can occur in versions of the Keras framework running versions 3.11.0 up to but not including 3.11.3, enabl
39Monitor
CVE-2026-12481326 days apartDeserialization of Untrusted Data in keras-team/keras
39Monitor
CVE-2025-990639 days apartArbitrary Code execution in Keras Safe Mode
34Monitor
CVE-2026-1462245 days apartSafe Mode Bypass in keras-team/keras
31Monitor
CVE-2025-1205879 days apartVulnerability in Keras Model.load_model Leading to Arbitrary Local File Loading and SSRF
23Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Someone with local access to the system can trigger it.
A low-privileged account is enough.
No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability

Attack vector: Local
Attack complexity: Low
Privileges required: Low
User interaction: P
Scope: X

Weakness class (CWE)

CWE-502 · Deserialization of Untrusted Data

CVSS vector

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:Y/R:A/V:X/RE:X/U:X

nvd-secondary

Root cause

Data received over the network is deserialized into the language’s native object format without verifying its source. Code paths inside the object can be triggered during deserialization.

The bug in code

The whole CWE-502 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

python

1payload = sock.recv(65536)
2job = pickle.loads(payload)

Fixed

python

1payload = sock.recv(65536)
2if not hmac.compare_digest(sign(payload), header_sig):
3    raise PermissionError("invalid signature")
4job = JobSchema.validate(json.loads(payload))