{"answers":{"affected":"1 open source package ship an affected version, including enum-map.","exploited":"There is no known exploitation of RUSTSEC-2026-0218 in the wild and no public exploit code.","fix":"Upgrade enum-map to 3.1.0 or later.","what":"RUSTSEC-2026-0218 is a memory corruption vulnerability in enum-map, published on 21 Jul 2026."},"fix_prompt":"Check this codebase for RUSTSEC-2026-0218 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0218 is a memory corruption vulnerability in enum-map, published on 21 Jul 2026. \nExploitation: There is no known exploitation of RUSTSEC-2026-0218 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- enum-map (crates.io): affected from 3.0.0-0.gat.0; fixed in 3.1.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/RUSTSEC-2026-0218/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0218/index.md)","id":"RUSTSEC-2026-0218","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0218/index.md","name":"RUSTSEC-2026-0218","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"unknown","non_default_config":false,"product_category":"Rust enum-map crate","requires_auth":"none","summary":"A type confusion vulnerability in the enum-map crate allows memory corruption when the Enum trait is manually implemented incorrectly.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"Affected versions of this crate did not require the element type of the `Array` associated type in the `Enum` trait to match the array's generic parameter `V`.\n\nThis can result in type confusion, and consequently memory corruption, when a manual `Enum` implementation declares an `Array\u003cV\u003e` whose elements are not actually of type `V`:\n\n```rust\nstruct IntentionallyWrong;\n\nimpl Enum for IntentionallyWrong {\n    type Array\u003cV\u003e = [String; 4];\n\n    fn from_usize(_: usize) -\u003e Self {\n        IntentionallyWrong\n    }\n\n    fn into_usize(self) -\u003e usize {\n        0\n    }\n}\n\nenum_map! { IntentionallyWrong =\u003e 42 };\n```\n\nThe flaw was corrected in commit [7a8b815432](https://codeberg.org/sugar700/enum-map/commit/7a8b8154323d426415a10accf104cd05c394cda9) by adding a `Value = V` bound to the `Array` type in the `Enum` trait.","ecosystems":["crates.io"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"`Enum` trait allows type confusion when manually implemented","id":"RUSTSEC-2026-0218","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["3.1.0"],"introduced":["3.0.0-0.gat.0"],"last_affected":[],"package":"enum-map","purl":"pkg:cargo/enum-map","source":"RUSTSEC-2026-0218"}],"products":null,"published":"2026-07-21","related":[],"sources":[{"class":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"A type confusion vulnerability in the enum-map crate allows memory corruption when the Enum trait is manually implemented incorrectly.","url":"https://insights.sbomify.com/RUSTSEC-2026-0218/"}