CVE-2026-12479

MEDIUMPre-NVD 6.16.1—
EchelonGraph scoreMEDIUM confidence

Score 6.1 from GitHub Security Advisory published 2026-06-22. a secondary CVSS source baseline 6.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
6.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A path traversal vulnerability exists in keras-team/keras version 3.14.0, specifically in the DiskIOStore.make method within the Keras 3 model saving and loading library. This vulnerability arises from the improper handling of user-provided layer names, which are used to construct directory paths without sanitizing for parent directory components (..). While forward slashes (/) are restricted in layer names, directory traversal sequences are not. This allows an attacker to craft a malicious Keras model that, when saved or loaded, can escape the intended temporary working directory and perform unauthorized file system operations, such as creating directories or writing files in arbitrary locations.

CVSS v3
6.1
EG Score
6.1MEDIUMmedium confidence
EG Risk
32
EG Risk 32/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
Severity61% × 45%
Exploitation0% × 40%
Automatability30% × 15%
EPSS PROB
0.4%
EPSS %ILE
30th
KEV
Not listed

Published

June 22, 2026

Last Modified

June 22, 2026

Advisory Details (1)

Auto-updated Jun 22, 2026
Patch available.
generic

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

https://huntr.com/bounties/188836b9-12fc-49c7-8dbf-04f60fe33743

Vendor Advisories for CVE-2026-12479(1)

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

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.12.3: fixed in 3.12.3
  • 3.13.0 up to 3.15.0: fixed in 3.15.0
—

Weakness Classification(1)

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

Data Freshness Timeline

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-12479?
CVE-2026-12479 is a medium vulnerability published on June 22, 2026. A path traversal vulnerability exists in keras-team/keras version 3.14.0, specifically in the DiskIOStore.make method within the Keras 3 model saving and loading library. This vulnerability arises from the improper handling of user-provided layer names, which are used to construct directory paths…
When was CVE-2026-12479 disclosed?
CVE-2026-12479 was first published on June 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-12479 actively exploited?
CVE-2026-12479 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (30th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-12479?
CVE-2026-12479 has a CVSS base score of 6.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-12479?
A fix for CVE-2026-12479 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-12479 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-12479

Explore →

Is Your Infrastructure Affected by CVE-2026-12479?

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

Book a Demo →Browse All CVEs