{"schema_version":"1.7.2","id":"OESA-2026-3236","modified":"2026-08-07T02:41:32Z","published":"2026-08-07T02:41:32Z","upstream":["CVE-2026-11816","CVE-2026-12482"],"summary":"python-Keras security update","details":"Keras is a high-level neural networks API for Python.\r\n\r\nSecurity Fix(es):\n\nKeras versions prior to 3.14.0 are vulnerable to a path traversal issue in the archive extraction utilities located in `keras/src/utils/file_utils.py`. The functions `filter_safe_tarinfos()` and `filter_safe_zipinfos()` validate archive member paths against the process current working directory (CWD) instead of the actual extraction destination. When the process runs with CWD set to `/`, which is common in Docker containers, CI/CD runners, and Jupyter environments, the validation boundary becomes the filesystem root, allowing traversal paths to bypass the security check. Additionally, the zip filter contains a bug that causes an `AttributeError` when a blocked entry is encountered, leading to incomplete extraction. Furthermore, Python 3.11 installations lack the `filter=&quot;data&quot;` safety net, leaving them entirely reliant on the flawed CWD-based filter. Exploitation of this vulnerability can result in arbitrary file writes outside the intended extraction directory, enabling attackers to overwrite configuration files, inject malicious code, or corrupt machine learning datasets and pipelines.(CVE-2026-11816)\n\nA vulnerability in keras-team/keras version 3.12.0 allows an attacker to craft a malicious tar archive that bypasses the `filter_safe_tarinfos` validation in `keras/src/utils/file_utils.py`. Specifically, symlink entries are not subjected to the same `is_path_in_dir` validation as regular file entries, allowing symlinks to be created outside the intended extraction directory. This can lead to symlink-based file read, file overwrite, or directory escape attacks. The issue is particularly impactful on Python 3.10 and 3.11, where `filter_safe_tarinfos` is the sole defense against tar path traversal. This vulnerability is distinct from CVE-2025-12060 and other previously reported issues.(CVE-2026-12482)","affected":[{"package":{"ecosystem":"openEuler:24.03-LTS-SP4","name":"python-Keras","purl":"pkg:rpm/openEuler/python-Keras&distro=openEuler-24.03-LTS-SP4"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.12.0-4.oe2403sp4"}]}],"ecosystem_specific":{"noarch":["python-Keras-help-2.12.0-4.oe2403sp4.noarch.rpm","python3-Keras-2.12.0-4.oe2403sp4.noarch.rpm"],"src":["python-Keras-2.12.0-4.oe2403sp4.src.rpm"]}}],"references":[{"type":"ADVISORY","url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-3236"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-11816"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-12482"}],"severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N"}],"database_specific":{"severity":"High"}}
