Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · RUSTSEC-2026-0218

`Enum` trait allows type confusion when manually implemented

No CVSS score

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.

PackageEcosystemAffectedFixed in
enum-mapcrates.io>=3.0.0-0.gat.0, <3.1.03.1.0
Identifiers
RUSTSEC-2026-0218
Published
21 Jul 2026
Updated
28 Jul 2026

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

  1. 31 Oct 2026, 15:18 UTC First seen by agentprime
  2. 31 Oct 2026, 15:18 UTC Confirmed by OSV

Sources

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.