The vulnerability can be triggered through both local and remote files
Keras · Keras
9.8CriticalCVSS 3.1
Recommended action
Within 72 hours
Critical technical impact with a remotely reachable, unauthenticated path and a public exploit reference; no CISA KEV confirmation is currently recorded.
Published severityCritical→Operational priority:Critical, unchanged from published severity.unchanged
Evidence used
No CISA KEV confirmation is currently recorded.
A structured source references public exploit or proof-of-concept material.
The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
EPSS is 0.75% for the current model date.
Compensating controls
Validate the affected product branch and deploy the verified fixed release.
Restrict the affected network interface to trusted sources where business-safe.
Increase monitoring for the attack path and post-exploitation behaviour described in the report.
Verification
Confirm that the asset runs Keras Keras and falls inside the recorded affected range.
Verify the installed build against the product-specific fixed version after deployment.
Validate exposure, authentication requirements and compensating controls in the actual environment.
Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Open-source package ranges1 source-attributed range
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
1 current
CVE-2025-49655 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykeras: Keras deserialization of untrusted data
52 fixed
The vendor explicitly identifies these products or versions as containing the fix.
registry.redhat.io/rhoai/odh-kserve-agent-rhel9@sha256:5a0d462e652464ae21e9152b6eac7d95c05d9d3d6884a3f1590c6194bda64ae7_ppc64le as a component of Red Hat OpenShift AI 2.25
registry.redhat.io/rhoai/odh-kserve-agent-rhel9@sha256:7caa5349317343219fa6a504ff80b04904df78adbc60b34a3b1951e072db513a_amd64 as a component of Red Hat OpenShift AI 2.25
registry.redhat.io/rhoai/odh-kserve-agent-rhel9@sha256:e744869b68de81c6a7fe9bc5a53676f2ea9ec6c72040cd5279f0b3c7a750dbc2_arm64 as a component of Red Hat OpenShift AI 2.25
registry.redhat.io/rhoai/odh-kserve-agent-rhel9@sha256:fc9ab886aa4b1c0b7083585c3edfb7ad6b3c748d8880bc425e049f0bbdec847b_s390x as a component of Red Hat OpenShift AI 2.25
registry.redhat.io/rhoai/odh-kserve-controller-rhel9@sha256:1148f10bdd5624ec3ec6e2099eaadf0192bbd4a7cb5758e71b20d811354204da_arm64 as a component of Red Hat OpenShift AI 2.25
registry.redhat.io/rhoai/odh-kserve-controller-rhel9@sha256:4bbfad1a5fde624a13c3edd27962e5b8bf7782ea4cd5f64b3a996d308e3be365_ppc64le as a component of Red Hat OpenShift AI 2.25
registry.redhat.io/rhoai/odh-kserve-controller-rhel9@sha256:8db8a21329d717f1783a346949a1de0a79b44b7c3cfdd4ec3e34604fb21c7d6a_amd64 as a component of Red Hat OpenShift AI 2.25
registry.redhat.io/rhoai/odh-kserve-controller-rhel9@sha256:c3627352344b43f17fe4ae467891b2ebd4332a642071b5ff3c0cf81d269f8280_s390x as a component of Red Hat OpenShift AI 2.25
registry.redhat.io/rhoai/odh-kserve-router-rhel9@sha256:605f8418c5c32d9a0936b4563a79fca6eeaef3bba7ca1b6abb91b0b1e84e4dd3_ppc64le as a component of Red Hat OpenShift AI 2.25
registry.redhat.io/rhoai/odh-kserve-router-rhel9@sha256:974dd5577124715f30df61d06aba22d95bc5f02103ab1b518eb517ed09284740_s390x as a component of Red Hat OpenShift AI 2.25
registry.redhat.io/rhoai/odh-kserve-router-rhel9@sha256:ba956e911769ebac40cb58b3ca4bb95b0bb7fd1f30d7210bc75498e95592fd98_arm64 as a component of Red Hat OpenShift AI 2.25
registry.redhat.io/rhoai/odh-kserve-router-rhel9@sha256:bdb164d90a0ad4cf3640afb518371e7b91c7682cc0b1e98e025ca1d64b927efc_amd64 as a component of Red Hat OpenShift AI 2.25
Summary
A unsafe deserialization flaw has been discovered in the Keras framework. An arbitrary code execution vulnerability exists in the TorchModuleWrapper class due to its usage of torch.load() within the from_config method. The method deserializes model data with the weights_only parameter set to False, which causes Torch to fall back on Python’s pickle module for deserialization. Since pickle is known to be unsafe and capable of executing arbitrary code during the deserialization process, a maliciously crafted model file could allow an attacker to execute arbitrary commands.
Remediation
For Red Hat OpenShift AI 2.25.1 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this errata update: https://docs.redhat.com/en/documentation/red_hat_openshift_ai/
Optional official sources
National CERT insights ?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.
Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.
Official European source
ENISA European Vulnerability Database
Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.
1 current
ENISA EUVD identifier
EUVD-2025-34892
No EUVD known-exploited evidence
ENISA has published the identifier mapping but no EUVD description has been stored yet.
EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 72 hours
Critical technical impact with a remotely reachable, unauthenticated path and a public exploit reference; no CISA KEV confirmation is currently recorded.
Patch available
01
What, why and how
Deserialization of untrusted data can occur in versions of the Keras framework running versions 3.11.0 up to but not including 3.11.3, enabling a maliciously uploaded Keras file containing a TorchModuleWrapper class to run arbitrary code on an end user’s system when loaded despite safe mode being enabled. The vulnerability can be triggered through both local and remote files.
What
Deserialization of untrusted data can occur in versions of the Keras framework running versions 3.11.0 up to but not including 3.11.3, enabling a maliciously uploaded Keras file containing a TorchModuleWrapper class to run arbitrary code on an end user’s system when loaded despite safe mode being enabled. The vulnerability can be triggered through both local and remote files.
Why
Attacker-influenced serialised data is reconstructed as trusted objects, which can invoke dangerous application behaviour.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may execute code or commands in the affected security context.
What
Deserialization of untrusted data can occur in versions of the Keras framework running versions 3.11.0 up to but not including 3.11.3, enabling a maliciously uploaded Keras file containing a TorchModuleWrapper class to run arbitrary code on an end user’s system when loaded despite safe mode being enabled. The vulnerability can be triggered through both local and remote files.
Why
Attacker-influenced serialised data is reconstructed as trusted objects, which can invoke dangerous application behaviour.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may execute code or commands in the affected security context.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation ?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No confirmed evidence
No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material ?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.Reference recorded
CISA Vulnrichment records proof-of-concept exploitation in its SSVC data. BlackTree has not independently executed or validated exploit material.
Likely attack path
a network path → Deserialization of Untrusted Data → execute code or commands in the affected security context
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness ?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-502: Deserialization of Untrusted Data. The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.
CVSS vector ?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.
Only matched European and national findings are included. Language selectors and unavailable sources are omitted.
ENISA EUVD · EUVD-2025-34892Official EUVD mapping
0 linked advisory records.
Official EUVD record ↗BSI · German · WID-SEC-2025-2673Red Hat OpenShift (Trusted Artifact Signer): Schwachstelle ermöglicht Codeausführung
Ein lokaler Angreifer kann eine Schwachstelle in Red Hat OpenShift ausnutzen, um beliebigen Programmcode auszuführen.
Official advisory ↗Cyber Security Agency of Singapore · English · CSA-SB-20251022Security Bulletin 22 Oct 2025
The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 22 Oct 2025, published on 22 October 2025. Open the linked bulletin for the product, severity and reference information published in that issue.
Operational remediation based on structured source evidence.
Status ?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
For Red Hat OpenShift AI 2.25.1 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this errata update: https://docs.redhat.com/en/documentation/red_hat_openshift_ai/
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04
Evidence and provenance
Published 17 Oct 2025 · Last source change 17 Oct 2025, 15:58 UTC · CWE-502 · Deserialization of Untrusted Data
CVE recordCVE.org · 5.1
CVSS sourceCNA
EPSS source ?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-34892
Product sourceCNA
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD not scheduled
Core structured fields are present and their contributing authorities are shown above.
Affected versionsThe structured affected or fixed version information changed.
Before
3.11.0 < 3.11.3 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
After
3.11.0 < 3.11.3 · Fixed: For Red Hat OpenShift AI 2.25.1 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this errata update: https://docs.redhat.com/en/documentation/red_hat_openshift_ai/
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.