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.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 8.1Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

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.1HIGHmedium confidence
EG Risk
52
EG Risk 52/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity81% × 45%
Exploitation40% × 40%
Automatability0% × 15%
EPSS PROB
0.6%
EPSS %ILE
45th
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

Vendor Advisories for CVE-2026-11816(4)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-modelmesh-runtime-adapter-rhel9:17833429002026-07-21redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
keras2.3.1+dfsg-3, 2.3.1+dfsg2-1
  • every version on: no fix on record
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
keras0.2.0 ... 3.9.2 (120 versions)
  • every version up to 3.14.0: fixed in 3.14.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 24× 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 271 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

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 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 0.6% probability of exploitation in the next 30 days (45th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-11816?
CVE-2026-11816 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-11816?
A fix for CVE-2026-11816 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-11816 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs