Arbitrary file writes via unchecked asset paths
Published Jun 22, 2026 · Updated Jun 22, 2026
Path traversal in Keras 3.14.0 allows attackers to write files outside the working directory by saving or loading a crafted model. DiskIOStore.make joins caller-controlled asset paths to its temporary working directory and creates them without checking that the resolved path stays inside. Exploitation requires a user to save or load the model, after which attacker-chosen paths can create directories or write files with that process's permissions.
Summary
What happened
Path traversal in Keras 3.14.0 allows attackers to write files outside the working directory by saving or loading a crafted model. DiskIOStore.make joins caller-controlled asset paths to its temporary working directory and creates them without checking that the resolved path stays inside. Exploitation requires a user to save or load the model, after which attacker-chosen paths can create directories or write files with that process's permissions.
The record
- CVE
- CVE-2026-12479
- Published
- Jun 22, 2026
- Updated
- Jun 22, 2026
- Vendor
- Keras
- Product
- Keras
- Classifications
- CWE-22, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 22, 2026CVE publishedPublication date reported by the CVE source.
- Jun 22, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <=latest
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- huntr.dev bounty proof of conceptproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo