CVE-2026-11816

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-06-11. a secondary CVSS source baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Elevated
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 8.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.1
EG Score
8.1(medium)
EPSS
43.4%
KEV
Not listed

Published

June 11, 2026

Last Modified

July 21, 2026

Advisory Details (2)

Auto-updated Jun 11, 2026
Patch available. Sources: github_commit.
generic

huntr - The world's first bug bounty platform for AI/ML

https://huntr.com/bounties/a07e3983-7158-4419-af2b-38f1dea01a4f
github_commit Patch Available

commit 2465b6657b02 (keras-team/keras)

Patch available: keras-team/keras v3.14.0 (contains commit 2465b6657b02)

https://github.com/keras-team/keras/commit/2465b6657b02c8eed308759b7e800e295ae01888

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
keras0.2.0 ... 3.9.2 (119 versions)3.14.0

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 74× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 111 total refreshes for this CVE.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:24 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-19 14:30 UTCEPSS rescore
  5. 2026-07-19 02:28 UTCEPSS rescore
  6. 2026-07-18 10:04 UTCEPSS rescore
  7. 2026-07-16 23:29 UTCGHSA enrichment
  8. 2026-07-16 17:02 UTCEPSS rescore
  9. 2026-07-16 10:25 UTCGHSA enrichment
  10. 2026-07-15 21:34 UTCGHSA enrichment
  11. 2026-07-15 16:57 UTCEPSS rescore
  12. 2026-07-15 07:58 UTCGHSA enrichment
  13. 2026-07-15 02:00 UTCEPSS rescore
  14. 2026-07-14 15:21 UTCGHSA enrichment
  15. 2026-07-14 02:26 UTCGHSA enrichment
  16. 2026-07-13 22:30 UTCEPSS rescore
  17. 2026-07-13 13:35 UTCGHSA enrichment
  18. 2026-07-13 06:12 UTCEPSS rescore
  19. 2026-07-12 22:26 UTCGHSA enrichment
  20. 2026-07-12 09:12 UTCGHSA enrichment
  21. 2026-07-12 05:46 UTCEPSS rescore
  22. 2026-07-11 20:20 UTCGHSA enrichment
  23. 2026-07-11 08:27 UTCEPSS rescore
  24. 2026-07-11 07:25 UTCGHSA enrichment
  25. 2026-07-10 17:48 UTCGHSA enrichment
Show 75 more
  1. 2026-07-09 19:10 UTCEPSS rescore
  2. 2026-07-09 12:38 UTCGHSA enrichment
  3. 2026-07-08 23:44 UTCGHSA enrichment
  4. 2026-07-08 15:15 UTCEPSS rescore
  5. 2026-07-08 15:15 UTCEPSS rescore
  6. 2026-07-08 10:52 UTCGHSA enrichment
  7. 2026-07-07 21:44 UTCGHSA enrichment
  8. 2026-07-07 13:46 UTCEPSS rescore
  9. 2026-07-07 03:10 UTCGHSA enrichment
  10. 2026-07-06 16:27 UTCEPSS rescore
  11. 2026-07-06 02:23 UTCEPSS rescore
  12. 2026-07-06 02:04 UTCGHSA enrichment
  13. 2026-07-05 13:10 UTCGHSA enrichment
  14. 2026-07-05 02:30 UTCEPSS rescore
  15. 2026-07-05 02:30 UTCEPSS rescore
  16. 2026-07-05 00:18 UTCGHSA enrichment
  17. 2026-07-04 11:25 UTCGHSA enrichment
  18. 2026-07-04 06:31 UTCEPSS rescore
  19. 2026-07-03 14:48 UTCGHSA enrichment
  20. 2026-07-03 01:04 UTCGHSA enrichment
  21. 2026-07-02 12:12 UTCGHSA enrichment
  22. 2026-07-01 23:12 UTCGHSA enrichment
  23. 2026-07-01 15:06 UTCEPSS rescore
  24. 2026-07-01 15:06 UTCEPSS rescore
  25. 2026-07-01 10:17 UTCGHSA enrichment
  26. 2026-06-30 23:22 UTCEPSS rescore
  27. 2026-06-30 21:25 UTCGHSA enrichment
  28. 2026-06-30 08:28 UTCGHSA enrichment
  29. 2026-06-29 19:35 UTCGHSA enrichment
  30. 2026-06-29 14:06 UTCEPSS rescore
  31. 2026-06-29 06:44 UTCGHSA enrichment
  32. 2026-06-28 15:42 UTCGHSA enrichment
  33. 2026-06-28 14:07 UTCEPSS rescore
  34. 2026-06-28 04:56 UTCEPSS rescore
  35. 2026-06-28 04:56 UTCEPSS rescore
  36. 2026-06-28 02:47 UTCGHSA enrichment
  37. 2026-06-27 13:55 UTCGHSA enrichment
  38. 2026-06-27 03:08 UTCEPSS rescore
  39. 2026-06-27 01:03 UTCGHSA enrichment
  40. 2026-06-26 12:11 UTCGHSA enrichment
  41. 2026-06-25 22:33 UTCGHSA enrichment
  42. 2026-06-25 13:49 UTCEPSS rescore
  43. 2026-06-25 09:38 UTCGHSA enrichment
  44. 2026-06-24 20:46 UTCGHSA enrichment
  45. 2026-06-24 14:05 UTCEPSS rescore
  46. 2026-06-24 04:20 UTCGHSA enrichment
  47. 2026-06-23 21:32 UTCEPSS rescore
  48. 2026-06-23 15:23 UTCGHSA enrichment
  49. 2026-06-23 02:04 UTCGHSA enrichment
  50. 2026-06-22 14:25 UTCEPSS rescore
  51. 2026-06-22 14:25 UTCEPSS rescore
  52. 2026-06-22 13:08 UTCGHSA enrichment
  53. 2026-06-22 00:04 UTCGHSA enrichment
  54. 2026-06-21 14:56 UTCEPSS rescore
  55. 2026-06-21 14:56 UTCEPSS rescore
  56. 2026-06-21 10:03 UTCGHSA enrichment
  57. 2026-06-21 01:59 UTCEPSS rescore
  58. 2026-06-21 01:59 UTCEPSS rescore
  59. 2026-06-20 20:31 UTCGHSA enrichment
  60. 2026-06-20 07:10 UTCGHSA enrichment
  61. 2026-06-19 19:25 UTCEPSS rescore
  62. 2026-06-19 18:02 UTCGHSA enrichment
  63. 2026-06-19 04:50 UTCGHSA enrichment
  64. 2026-06-18 17:52 UTCEPSS rescore
  65. 2026-06-18 15:50 UTCGHSA enrichment
  66. 2026-06-18 02:18 UTCGHSA enrichment
  67. 2026-06-17 17:53 UTCEPSS rescore
  68. 2026-06-17 13:26 UTCGHSA enrichment
  69. 2026-06-17 00:34 UTCGHSA enrichment
  70. 2026-06-16 17:52 UTCEPSS rescore
  71. 2026-06-16 11:43 UTCGHSA enrichment
  72. 2026-06-15 22:51 UTCGHSA enrichment
  73. 2026-06-15 17:48 UTCEPSS rescore
  74. 2026-06-15 10:00 UTCGHSA enrichment
  75. 2026-06-14 23:18 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-11816?
CVE-2026-11816 is a high vulnerability published on June 11, 2026. Keras versions prior to 3.14.0 are vulnerable to a path traversal issue in the archive extraction utilities located in keras/src/utils/fileutils.py. The functions filtersafetarinfos() and filtersafe_zipinfos() validate archive member paths against the process current working directory (CWD) instead…
When was CVE-2026-11816 disclosed?
CVE-2026-11816 was first published in the National Vulnerability Database on June 11, 2026, with the most recent update on July 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-11816 actively exploited?
CVE-2026-11816 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 43.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-11816?
CVE-2026-11816 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-11816?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-11816, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-11816

Explore →

Is Your Infrastructure Affected by CVE-2026-11816?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.