keras-team keras up to 3.12.1/3.14.0 file_editor.py H5IOStore._verify_dataset file inclusion

Summaryinfo

A vulnerability categorized as problematic has been discovered in keras-team keras up to 3.12.1/3.14.0. This vulnerability affects the function H5IOStore._verify_dataset of the file file_editor.py. The manipulation results in file inclusion. This vulnerability is reported as CVE-2026-12480. The attack requires a local approach. No exploit exists. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability classified as problematic has been found in keras-team keras up to 3.12.1/3.14.0. Affected is the function H5IOStore._verify_dataset of the file file_editor.py. The manipulation with an unknown input leads to a file inclusion vulnerability. CWE is classifying the issue as CWE-73. The product allows user input to control or influence paths or file names that are used in filesystem operations. This is going to have an impact on confidentiality. CVE summarizes:

Keras versions up to and including 3.13.2 are vulnerable to an arbitrary HDF5 file read due to an incomplete fix for CVE-2026-1669. The vulnerability resides in the `H5IOStore._verify_dataset()` and `file_editor.py` methods, which fail to check the `dataset.is_virtual` property of HDF5 datasets. This allows an attacker to craft a malicious `.keras` model archive or `.h5` weights file containing a Virtual Dataset (VDS) that references external HDF5 files on the victim's filesystem. When the victim loads the model using `keras.models.load_model()` or `keras.saving.load_model()`, the external file is transparently read, leading to potential information disclosure. Fixed in versions 3.12.2 and 3.14.1.

The advisory is available at huntr.com. This vulnerability is traded as CVE-2026-12480 since 06/17/2026. The exploitability is told to be easy. Local access is required to approach this attack. Successful exploitation requires user interaction by the victim. Technical details are known, but there is no available exploit.

Upgrading to version 3.12.2 or 3.14.1 eliminates this vulnerability. Applying the patch d5a88bdb137c0d3039b8f4bbbe8c7099925cc10c is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Vendor

• keras-team

Name

• keras

Version

• 3.0
• 3.1
• 3.2
• 3.3
• 3.4
• 3.5
• 3.6
• 3.7
• 3.8
• 3.9
• 3.10
• 3.11
• 3.12
• 3.12.0
• 3.12.1
• 3.13
• 3.14.0

License

• open-source

Website

• Product: https://github.com/keras-team/keras/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion