{"answers":{"affected":"5 open source packages ship an affected version, including keras.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-12480 exists.","fix":"Upgrade keras to a fixed version for your release line: 3.12.3 or 3.15.0.","what":"CVE-2026-12480 is a medium-severity path traversal vulnerability in keras-team/keras, published on 1 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-12480 and fix it if it is affected.\n\nWhat it is: CVE-2026-12480 is a medium-severity path traversal vulnerability in keras-team/keras, published on 1 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-12480 exists.\n\nAffected packages and fixed versions:\n- keras (PyPI): affected all versions; fixed in 3.12.3, 3.15.0\n- keras (PyPI): affected all versions; fixed in 3.12.3\n- keras (PyPI): affected all versions; fixed in 3.12.3\n- keras (PyPI): affected from 3.13.0; fixed in 3.15.0\n- keras (PyPI): affected from 3.13.0; fixed in 3.15.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-12480/ (Markdown: https://insights.sbomify.com/CVE-2026-12480/index.md)","id":"CVE-2026-12480","markdown":"https://insights.sbomify.com/CVE-2026-12480/index.md","name":"CVE-2026-12480","record":{"aliases":["AZL-92027","DEBIAN-CVE-2026-12480","GHSA-26c4-7vv6-867j","MINI-53c4-pr5f-8h8m","PYSEC-2026-3629","UBUNTU-CVE-2026-12480"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Keras deep learning library","requires_auth":"none","summary":"Attackers can read arbitrary files from the victim's filesystem by crafting malicious Keras model files that exploit virtual dataset handling flaws.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntr_ai","cpe":[],"cvss":{"score":5.5,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-73","name":"External Control of File Name or Path"}],"description":"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Arbitrary HDF5 File Read via Virtual Dataset Bypass in keras-team/keras","id":"CVE-2026-12480","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":5,"n_references":2,"next":{"headline":"Deserialization of Untrusted Data in keras-team/keras","id":"CVE-2026-12481"},"packages":[{"ecosystem":"PyPI","fixed":["3.12.3","3.15.0"],"introduced":["0","3.13.0"],"last_affected":[],"package":"keras","purl":"pkg:pypi/keras","source":"PYSEC-2026-3629"},{"ecosystem":"PyPI","fixed":["3.12.3"],"introduced":["0"],"last_affected":[],"package":"keras","purl":null,"source":"GHSA-26c4-7vv6-867j"},{"ecosystem":"PyPI","fixed":["3.12.3"],"introduced":["0"],"last_affected":[],"package":"keras","purl":"pkg:pypi/keras","source":"GHSA-26c4-7vv6-867j"},{"ecosystem":"PyPI","fixed":["3.15.0"],"introduced":["3.13.0"],"last_affected":[],"package":"keras","purl":null,"source":"GHSA-26c4-7vv6-867j"},{"ecosystem":"PyPI","fixed":["3.15.0"],"introduced":["3.13.0"],"last_affected":[],"package":"keras","purl":"pkg:pypi/keras","source":"GHSA-26c4-7vv6-867j"}],"prev":{"headline":"Path Traversal in keras-team/keras","id":"CVE-2026-12479"},"products":["keras-team/keras"],"published":"2026-07-01","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-01","vendors":["keras-team"]},"summary":"Attackers can read arbitrary files from the victim's filesystem by crafting malicious Keras model files that exploit virtual dataset handling flaws.","url":"https://insights.sbomify.com/CVE-2026-12480/"}