# Keras has a Local File Disclosure via HDF5 External Storage During Keras Weight Loading

Advisory record · `GHSA-3m4q-jmj6-r34q`

- **Identifiers:** `GHSA-3m4q-jmj6-r34q` · `CVE-2026-1669` · `PYSEC-2026-2546`
- **State:** Confirmed
- **Severity:** CVSS 7.1 High
- **Critical:** No
- **Weakness (CWE):** [CWE-73](https://cwe.mitre.org/data/definitions/73.html) · [CWE-200](https://cwe.mitre.org/data/definitions/200.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md) · [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md)
- **Published:** 18 Feb 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 18 Feb 2026, 22:41 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `keras` (PyPI): affected `>=3.13.0, <3.13.2 || >=3.0.0, <3.12.1`; fixed in `3.13.2`, `3.12.1`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Keras versions from 3.0.0 before 3.12.1, and from 3.13.0 before 3.13.2, are affected. When loading weights, Keras follows HDF5 external storage and external link references in a crafted weights file or \`.keras\` archive, which can expose the contents of arbitrary readable files on the host. A victim must load an attacker-supplied file; the leaked bytes can then appear in model outputs or in re-saved artifacts. Upgrade to Keras 3.12.1 or 3.13.2. Avoid loading untrusted weight files.

Written 5 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.1 High, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`, from CNA (Google)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0033, the 26th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:34 UTC: First seen by agentprime
- 31 Oct 2026, 14:34 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-3m4q-jmj6-r34q)

## Sources

- [GitHub Advisory Database: GHSA-3m4q-jmj6-r34q](https://github.com/advisories/GHSA-3m4q-jmj6-r34q)
- [OSV: GHSA-3m4q-jmj6-r34q](https://osv.dev/vulnerability/GHSA-3m4q-jmj6-r34q)
- <https://github.com/keras-team/keras/security/advisories/GHSA-3m4q-jmj6-r34q>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-1669>
- <https://github.com/keras-team/keras/pull/22057>
- <https://github.com/keras-team/keras/commit/8a37f9dadd8e23fa4ee3f537eeb6413e75d12553>
- <https://github.com/keras-team/keras>
- <https://github.com/keras-team/keras/releases/tag/v3.12.1>
- <https://github.com/keras-team/keras/releases/tag/v3.13.2>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-3m4q-jmj6-r34q>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-3m4q-jmj6-r34q/>. Everything for agents: <https://agentprime.io/llms.txt>.
