# \`Enum\` trait allows type confusion when manually implemented

Advisory record · `RUSTSEC-2026-0218`

- **Identifiers:** `RUSTSEC-2026-0218`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **Published:** 21 Jul 2026
- **Updated:** 28 Jul 2026
- **Reviewed by a person:** No

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

## Affected packages

- `enum-map` (crates.io): affected `>=3.0.0-0.gat.0, <3.1.0`; fixed in `3.1.0`

## Machine-written summary

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

> The enum-map crate, versions 3.0.0-0.gat.0 up to but not including 3.1.0, has a type confusion flaw in its Enum trait when the trait is implemented manually. The Array associated type was not required to hold elements of the generic parameter V, so a manual implementation can cause memory corruption. Upgrade enum-map to version 3.1.0 or later; the source gives no workaround.

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-0218)

## Sources

- [OSV: RUSTSEC-2026-0218](https://osv.dev/vulnerability/RUSTSEC-2026-0218)
- <https://crates.io/crates/enum-map>
- <https://rustsec.org/advisories/RUSTSEC-2026-0218.html>
- <https://codeberg.org/sugar700/enum-map/src/branch/master/CHANGELOG.md#version-310>

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