How many CVEs have a located fix in keras-team/keras?

19 published CVEs have a fix traced to functions in keras-team/keras, touching 52 functions across 18 files.

Which function in keras-team/keras has been patched by the most CVEs?

extract_open_archive in keras/src/utils/file_utils.py has been changed by 4 CVE fixes, from 2025 to 2026.

How large is a typical CVE fix in keras-team/keras?

The median fix changes 40 lines. 21% of fixes change 20 lines or fewer, and 11% change a single function.

How is a fix located to a function?

The upstream fix commit for each CVE is fetched and its diff is split into hunks. Each hunk is attributed to the function, method or type it changes, using the definition the diff itself names. Backports of the same fix to stable branches are counted once.

RadicalNotion.AI

Log in Create an account

python

#281 of 500 repositories

keras-team/keras

Name: keras-team/keras: functions patched by CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

Functions and files changed by CVE fixes in this repository.

Latest located fix August 10, 2026

19

CVE fixes located

Published CVEs

52

Functions patched

Distinct function sites

18

Files patched

Distinct source files

2025–2026

Years covered

By CVE publication date

Overview

19 published CVEs have a fix traced to functions in keras-team/keras, the earliest published in 2025. Those fixes changed 52 distinct functions across 18 files, in 257 patch hunks.

Among the 500 repositories tracked here, keras-team/keras ranks #281 by the number of CVEs with a located fix.

Most patched functions

Functions in keras-team/keras changed by the most CVE fixes.

Most patched files

Files in keras-team/keras changed by the most CVE fixes.

1keras/src/saving/saving_lib.py9 CVEs · 12 functions
2keras/src/utils/file_utils.py5 CVEs · 8 functions
3keras/src/legacy/saving/legacy_h5_format.py4 CVEs · 7 functions
4keras/src/saving/serialization_lib.py4 CVEs · 2 functions
5keras/src/saving/file_editor.py4 CVEs · 1 functions
6keras/src/utils/torch_utils.py4 CVEs · 1 functions
7keras/src/legacy/saving/saving_utils.py3 CVEs · 3 functions
8keras/src/layers/core/lambda_layer.py3 CVEs · 2 functions
9keras/src/layers/preprocessing/feature_space.py2 CVEs · 3 functions
10keras/src/models/functional.py2 CVEs · 2 functions

Fix size

How much code a CVE fix in keras-team/keras changes, with backports counted once.

40

Median lines changed

Added plus removed, per CVE

21%

Fixes of 20 lines or fewer

Share of CVE fixes

11%

Fixes in a single function

Share of CVE fixes

Latest CVEs

The most recently published CVEs with a fix located in keras-team/keras, and the functions each fix changed.

Denial of Service via HDF5 Shape Bomb in keras.models.load_model() in keras-team/keras
CVE-2026-12570safe_get_h5_dataset safe_get_h5_group
Medium · CVSS 5.5
EPSS 0.1%2026-08-10
Improper Handling of HDF5 ExternalLinks in keras-team/keras
CVE-2026-9335_extract_weights_from_store
Medium · CVSS 6.5
EPSS 0.8%2026-08-02
Unsafe Deserialization in keras.layers.TorchModuleWrapper.from_config
CVE-2026-12484from_config
High · CVSS 7.8
EPSS 0.4%2026-07-19
Path Traversal via Symlink Name Validation Bypass in keras-team/keras
CVE-2026-12482resolve_path
Medium · CVSS 6.5
EPSS 0.3%2026-07-14
Deserialization of Untrusted Data in keras-team/keras
CVE-2026-12481from_config
Critical · CVSS 9.8
EPSS 0.7%2026-07-03
Arbitrary HDF5 File Read via Virtual Dataset Bypass in keras-team/keras
CVE-2026-12480safe_get_h5_group get load_weights_from_hdf5_group
Medium · CVSS 5.5
EPSS 0.2%2026-07-01
Path Traversal in keras-team/keras
CVE-2026-12479_full_path get
Medium · CVSS 6.1
EPSS 0.4%2026-06-22
Path Traversal in keras-team/keras
CVE-2026-11816extract_open_archive filter_safe_tarinfos filter_safe_zipinfos
High · CVSS 8.1
EPSS 0.6%2026-06-11
Safe Mode Bypass in keras-team/keras
CVE-2026-1462from_config
High · CVSS 7.8
EPSS 0.4%2026-04-13
Arbitrary File Read in Keras via HDF5 External Datasets
CVE-2026-1669items _verify_group get
High · CVSS 7.1
EPSS 0.3%2026-02-11
Denial of Service in Keras via Excessive Memory Allocation in HDF5 Metadata
CVE-2026-0897_extract_weights_from_store items from_config
High · CVSS 7.1
EPSS 0.3%2026-01-15
Path Traversal Vulnerability in keras-team/keras via Tar Archive Extraction in keras.utils.get_file()
CVE-2025-12638extract_open_archive filter_safe_paths extract_archive
High · CVSS 8.0
EPSS 0.7%2025-11-28

Get an alert for each new keras-team/keras CVE, with the patched functions and AI-written analysis.

Monitor keras CVEs

Other repositories

Repositories with a similar number of located CVE fixes.

1Panel-dev/MaxKB19 CVEs alextselegidis/easyappointments19 CVEs baserproject/basercms19 CVEs bookstackapp/bookstack19 CVEs cloudfoundry/uaa19 CVEs debian/dovecot19 CVEs debian/nginx19 CVEs debian/openimageio19 CVEs

Browse all repositories

Frequently asked questions

Common questions about CVE fixes in keras-team/keras.

How many CVEs have a located fix in keras-team/keras?: 19 published CVEs have a fix traced to functions in keras-team/keras, touching 52 functions across 18 files.
Which function in keras-team/keras has been patched by the most CVEs?: extract_open_archive in keras/src/utils/file_utils.py has been changed by 4 CVE fixes, from 2025 to 2026.
How large is a typical CVE fix in keras-team/keras?: The median fix changes 40 lines. 21% of fixes change 20 lines or fewer, and 11% change a single function.
How is a fix located to a function?: The upstream fix commit for each CVE is fetched and its diff is split into hunks. Each hunk is attributed to the function, method or type it changes, using the definition the diff itself names. Backports of the same fix to stable branches are counted once.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track keras-team/keras CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing