# Panic-safety unsoundness in \`Chunk\` and \`InlineArray\` (use-after-free / double-free)

Advisory record · `RUSTSEC-2026-0254`

- **Identifiers:** `RUSTSEC-2026-0254`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **Published:** 11 Aug 2026
- **Updated:** 12 Aug 2026
- **Reviewed by a person:** No

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

## Affected packages

- `sp-sized-chunks` (crates.io): affected `>=0.0.0-0`; no fixed version yet

## Machine-written summary

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

> Versions of sp-sized-chunks from 0.0.0 onward are affected, and no fixed version is listed. Several methods drop elements before updating the container's length metadata, so if an element's Drop panics, the container later drops those already-freed elements again, causing use-after-free or double-free. The source describes this as reachable from safe Rust using catch_unwind with element types whose Drop can panic. No workaround is given, and the repository is archived.

Written 8 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, 15:18 UTC: First seen by agentprime
- 31 Oct 2026, 15:18 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/RUSTSEC-2026-0254)

## Sources

- [OSV: RUSTSEC-2026-0254](https://osv.dev/vulnerability/RUSTSEC-2026-0254)
- <https://crates.io/crates/sp-sized-chunks>
- <https://rustsec.org/advisories/RUSTSEC-2026-0254.html>

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-0254>, 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-0254/>. Everything for agents: <https://agentprime.io/llms.txt>.
