Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.7amended

The Keras Model.load_model method **silently** ignores safe_mode=True and allows arbitrary code execution when a .h5/.hdf5 file is loaded.

CVE-2025-9905GHSA-36rr-ww3j-vrjv

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (keras 3.11.3), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI keras

    Affected
    >= 3.0.0, < 3.11.3
    Fixed in
    3.11.3

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
8.7 · CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H · score source
EPSS
  • CVE-2025-9905: 0.22% estimated exploitation activity in the next 30 days; percentile 12.78 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Note: This report has already been discussed with the Google OSS VRP team, who recommended that I reach out directly to the Keras team. I’ve chosen to do so privately rather than opening a public issue, due to the potential security implications. I also attempted to use the email address listed in your SECURITY.md, but received no response. --- Summary When a model in the .h5 (or .hdf5) format is loaded using the Keras Model.loadmodel method, the safemode=True setting is silently ignored without any warning or error. This allows an attacker to execute arbitrary code on the victim’s machine with the same privileges as the Keras application. This report is specific to the .h5/.hdf5 file format. The attack works regardless of the other parameters passed to loadmodel and does not require any sophisticated technique—.h5 and .hdf5 files are simply not checked for unsafe code execution. From this point on, I will refer only to the .h5 file format, though everything equally applies to .hdf5.…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-36rr-ww3j-vrjv

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-36rr-ww3j-vrjv

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-9905

Advisory: The Keras `Model.load_model` method **silently** ignores `safe_mode=True` and allows arbitrary code execution when a `.h5`/`.hdf5` file is loaded.
IDs: CVE-2025-9905, GHSA-36rr-ww3j-vrjv
Record: https://patchnext.com/advisories/cve-2025-9905 (revision 3, source checked 26 Oct 2026, 13:44 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: keras 3.11.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI keras: affected >= 3.0.0, < 3.11.3; fixed in 3.11.3

## Suggested inspection (read-only)
- `python -m pip show keras`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on keras.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-36rr-ww3j-vrjv (OSV record GHSA-36rr-ww3j-vrjv lists affected ranges: PyPI keras >=3.0.0 <3.11.3 (fixed))
- Verified: https://github.com/advisories/GHSA-36rr-ww3j-vrjv (GitHub-reviewed advisory GHSA-36rr-ww3j-vrjv lists affected ranges: PyPI keras >=3.0.0 <3.11.3)

Commands are suggestions: review each one before running it.

Loading voting…