{"answers":{"affected":"3 open source packages ship an affected version, including keras. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-8747 exists.","fix":"Upgrade keras to 3.11.0 or later.","what":"CVE-2025-8747 is a high-severity unsafe deserialization vulnerability in Google Keras, published on 11 Aug 2025. 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-2025-8747 and fix it if it is affected.\n\nWhat it is: CVE-2025-8747 is a high-severity unsafe deserialization vulnerability in Google Keras, published on 11 Aug 2025. 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-2025-8747 exists.\n\nAffected packages and fixed versions:\n- keras (PyPI): affected all versions; no fix listed\n- keras (PyPI): affected from 3.0.0; fixed in 3.11.0\n- keras (PyPI): affected from 3.0.0; fixed in 3.11.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-2025-8747/ (Markdown: https://insights.sbomify.com/CVE-2025-8747/index.md)","id":"CVE-2025-8747","markdown":"https://insights.sbomify.com/CVE-2025-8747/index.md","name":"CVE-2025-8747","record":{"aliases":["AZL-66171","GHSA-c9rc-mg46-23w3","PYSEC-2025-75","UBUNTU-CVE-2025-8747"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Keras deep learning library","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary code by tricking users into loading malicious Keras model files, bypassing safe mode protections.","user_interaction":"required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Google","cpe":[{"product":"keras","vendor":"keras"}],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/AU:Y/R:A","version":"4.0"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"A safe mode bypass vulnerability in the `Model.load_model` method in Keras versions 3.0.0 through 3.10.0 allows an attacker to achieve arbitrary code execution by convincing a user to load a specially crafted `.keras` model archive.","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":"Keras safe_mode bypass allows arbitrary code execution when loading a malicious model.","id":"CVE-2025-8747","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"deserialization","year":"2025"},"n_packages":3,"n_references":2,"next":{"headline":"OS command injection in MiR robots and MiR fleet via crafted HTTP requests","id":"CVE-2025-8748"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":[],"last_affected":[],"package":"keras","purl":"pkg:pypi/keras","source":"PYSEC-2025-75"},{"ecosystem":"PyPI","fixed":["3.11.0"],"introduced":["3.0.0"],"last_affected":[],"package":"keras","purl":null,"source":"GHSA-c9rc-mg46-23w3"},{"ecosystem":"PyPI","fixed":["3.11.0"],"introduced":["3.0.0"],"last_affected":[],"package":"keras","purl":"pkg:pypi/keras","source":"GHSA-c9rc-mg46-23w3"}],"prev":{"headline":"GNU libopts __strstr_sse2 memory corruption","id":"CVE-2025-8746"},"products":["Keras"],"published":"2025-08-11","related":[{"cvss_score":9.8,"headline":"Arbitrary code injection vulnerability in Keras framework \u003c 2.13","id":"CVE-2024-3660","kev_date_added":null,"published":"2024-04-16"},{"cvss_score":8.8,"headline":"Deserialization of Untrusted Data in keras-team/keras","id":"CVE-2026-12481","kev_date_added":null,"published":"2026-07-03"},{"cvss_score":8.8,"headline":"Safe Mode Bypass in keras-team/keras","id":"CVE-2026-1462","kev_date_added":null,"published":"2026-04-13"},{"cvss_score":8.6,"headline":"Arbitrary Code execution in Keras Safe Mode","id":"CVE-2025-9906","kev_date_added":null,"published":"2025-09-19"},{"cvss_score":8.1,"headline":"Path Traversal in keras-team/keras","id":"CVE-2026-11816","kev_date_added":null,"published":"2026-06-11"},{"cvss_score":7.3,"headline":"Arbitary Code execution in Keras load_model()","id":"CVE-2025-9905","kev_date_added":null,"published":"2025-09-19"}],"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":"US public information, NVD API terms","name":"NVD"},{"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":"total"},"state":"PUBLISHED","updated":"2026-02-26","vendors":["Google"]},"summary":"Attackers can execute arbitrary code by tricking users into loading malicious Keras model files, bypassing safe mode protections.","url":"https://insights.sbomify.com/CVE-2025-8747/"}