# \`Seekable\` reads a NULL or out-of-bounds seek table

Advisory record · `RUSTSEC-2026-0396`

- **Identifiers:** `RUSTSEC-2026-0396`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **Published:** 16 Oct 2026
- **Updated:** 2 Nov 2026
- **Reviewed by a person:** No

Published by OSV at 16 Oct 2026, 12:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `zstd-safe` (crates.io): affected `>=7.2.2, <7.4.0 || >=8.0.0-0, <8.2.0`; fixed in `7.4.0`, `8.2.0`

## Machine-written summary

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

> Versions of zstd-safe from 7.2.2 before 7.4.0, and from 8.0.0 before 8.2.0, are affected. On a fresh Seekable, or after a failed init_buff() call, decompress, offset_to_frame_index and frame_decompressed_size can read a NULL seek table, and after a failed re-initialization decompress can return data from the refused buffer. Also, frame_decompressed_size(num_frames()) reads one entry past the end of the seek table on Seekable and SeekTable. The source gives few details on the attacker's position or impact. Upgrade to zstd-safe 7.4.0 or 8.2.0.

Written 3 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

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** No score.

## Timeline

- 31 Oct 2026, 14:24 UTC: First seen by agentprime
- 31 Oct 2026, 14:24 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/RUSTSEC-2026-0396)

## Sources

- [OSV: RUSTSEC-2026-0396](https://osv.dev/vulnerability/RUSTSEC-2026-0396)
- <https://crates.io/crates/zstd-safe>
- <https://rustsec.org/advisories/RUSTSEC-2026-0396.html>
- <https://github.com/gyscos/zstd-rs/commit/a9626069d6f2e90b782b8f627f57a361cfe8ef85>
- <https://github.com/gyscos/zstd-rs/pull/384>

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/RUSTSEC-2026-0396>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/RUSTSEC-2026-0396/>. Everything for agents: <https://agentprime.io/llms.txt>.
