{
  "affected": [
    {
      "database_specific": {
        "categories": [
          "memory-corruption"
        ],
        "cvss": null,
        "informational": "unsound"
      },
      "ecosystem_specific": {
        "affected_functions": null,
        "affects": {
          "arch": [],
          "functions": [],
          "os": []
        }
      },
      "package": {
        "ecosystem": "crates.io",
        "name": "emap",
        "purl": "pkg:cargo/emap"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0.0.0-0"
            }
          ],
          "type": "SEMVER"
        }
      ],
      "versions": []
    }
  ],
  "aliases": [],
  "database_specific": {
    "license": "CC0-1.0"
  },
  "details": "`Keys::next()` uses `ptr::read` to move out the `Option\u003cV\u003e` by value, which\ndrops the contained `V` when `V` is non-Copy (e.g. `String`). This leaves a\ndangling value in the map\u0027s storage slot. Subsequent `get()` operations on\nthat key return a dangling reference to already-freed memory.\n\nThis can be triggered through safe public APIs \u2014 `Map::keys()`,\n`Keys::next()`, and `Map::get()` \u2014 with no `unsafe` required from the\ncaller. Under Miri, accessing the freed slot produces \"Undefined Behavior:\npointer not dereferenceable: alloc has been freed, so this pointer is\ndangling\".",
  "id": "RUSTSEC-2026-0128",
  "modified": "2026-05-13T12:19:05Z",
  "published": "2026-05-02T12:00:00Z",
  "references": [
    {
      "type": "PACKAGE",
      "url": "https://crates.io/crates/emap"
    },
    {
      "type": "ADVISORY",
      "url": "https://rustsec.org/advisories/RUSTSEC-2026-0128.html"
    },
    {
      "type": "REPORT",
      "url": "https://github.com/yegor256/emap/issues/168"
    }
  ],
  "related": [],
  "severity": [],
  "summary": "Double-free and use-after-free in `Keys::next()`"
}