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
Trending — 3 sources updated this weekElevated
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.1Exploit: Elevated riskExposed: 0

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.1(medium)
EG Risk
52(Track*)
EG Risk 52/100SSVC: Track*

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%
Action: Watch closely — could escalate to Attend.
EPSS PROB
1%
EPSS %ILE
44%
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(3)

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 / EcosystemFixed in / 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 rangeFixed inDependents
keras2.3.1+dfsg-3, 2.3.1+dfsg2-1——
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 15× in last 7d / 110× 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 233 total refreshes for this CVE.

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

Related CVEs(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 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 1% probability of exploitation in the next 30 days, which ranks it in the top 55.6% of all scored CVEs.
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.

Start Free Scan →Browse All CVEs