CVE-2026-11816 Details
Description
Keras 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="data"` 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.
A path traversal vulnerability has been identified in Keras versions prior to 3.14.0, specifically within the archive extraction utilities in 'keras/src/utils/file_utils.py'. The issue arises because the functions 'filter_safe_tarinfos()' and 'filter_safe_zipinfos()' validate archive member paths against the current working directory (CWD) instead of the actual extraction destination. This flaw is particularly exploitable when the CWD is set to '/', a common scenario in Docker containers, CI/CD runners, and Jupyter environments. Under these conditions, the validation bypasses security checks, allowing traversal paths to manipulate files outside the intended directory. The vulnerability can lead to overwriting configuration files, injecting malicious code, or corrupting machine learning datasets and pipelines.
Users can upgrade to Keras version 3.14.0 or later, where this vulnerability has been fixed.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Jun 11, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://access.redhat.com/errata/RHSA-2026:42644 | redhat-SADP | |
| https://access.redhat.com/security/cve/CVE-2026-11816 | redhat-SADP | MitigationThird Party Advisory |
| https://bugzilla.redhat.com/show_bug.cgi?id=2487912 | redhat-SADP | Third Party Advisory |
| https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-11816.json | redhat-SADP | Third Party Advisory |
| https://huntr.com/bounties/a07e3983-7158-4419-af2b-38f1dea01a4f | CISA-ADP | ExploitThird Party Advisory |
| https://github.com/keras-team/keras/commit/2465b6657b02c8eed308759b7e800e295ae01888 | [email protected] | Patch |
| https://huntr.com/bounties/a07e3983-7158-4419-af2b-38f1dea01a4f | [email protected] | ExploitThird Party Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-22 | Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') | redhat-SADP |
| CWE-22 | Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| keras keras | < 3.14.0 |
CPE
Remediation
| |
Change History
9 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 26, 2026 | CVE Translated | [email protected] |
| Jul 21, 2026 | CVE Modified | redhat-SADP |
| Jul 15, 2026 | CVE Modified | redhat-SADP |
| Jul 1, 2026 | Initial Analysis | [email protected] |
| Jun 30, 2026 | CVE Modified | redhat-SADP |
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Jun 11, 2026 | CVE Modified | CISA-ADP |
| Jun 11, 2026 | New CVE Received | [email protected] |