dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-12479

MEDIUM · 6.1 CVSS v3.0 Published 2026-06-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
64/100
Remediation priority · Elevated
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A path traversal vulnerability exists in keras-team/keras version 3.14.0 in the DiskIOStore.make method where user-provided layer names are used to construct directory paths without sanitizing directory traversal sequences (..). While forward slashes are blocked in layer names, the .. sequence is not, allowing attackers to escape the intended temporary working directory and perform unauthorized file system operations such as creating directories or writing files to arbitrary locations.

MitigationImplement input validation to strip or block directory traversal sequences (..) from layer names and add path boundary checks to ensure constructed paths remain within the intended working directory.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Keras version
    Run 'pip show keras' or 'import keras; print(keras.__version__)' to identify the installed Keras version
    Affected if Version is 3.14.0 exactly (the only affected version listed)
  2. Identify if DiskIOStore is in use
    Search codebase for imports or references to 'DiskIOStore' class, particularly the '.make' method - this is used in Keras 3.x for model disk I/O operations
    Affected if Code uses DiskIOStore.make method from keras team/keras version 3.14.0
  3. Locate code passing layer names to DiskIOStore.make
    Search for calls to DiskIOStore.make and trace whether layer_name parameters are user-controlled (e.g., from API input, config files, or model metadata)
    Affected if Layer names provided to DiskIOStore.make originate from untrusted input without validation
  4. Inspect layer name handling for traversal sequences
    Review code that accepts or processes layer names before passing to DiskIOStore.make - specifically look for lack of filtering of '..' sequences
    Affected if Layer names are not validated to remove or block '..' directory traversal sequences
  5. Verify forward slash blocking is insufficient
    Confirm that while layer names may block forward slashes (/), the '..' sequence is not explicitly blocked or sanitized
    Affected if Only forward slashes are blocked but '..' sequences remain unfiltered in layer name validation

You are affected if running Keras 3.14.0 and your code passes user-influenced layer names to DiskIOStore.make without filtering '..' sequences, allowing path traversal outside the intended working directory.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement input validation to strip or block directory traversal sequences (..) from layer names and add path boundary checks to ensure constructed paths remain within the intended working directory.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-12479 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-12479 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data