{
  "id": "CVE-2026-87874",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-87874",
  "published_at": "2026-09-09T16:06:22.995Z",
  "title": "Community.general: community.general: memcached cache plugin deserializes untrusted pickle data from memcached, enabling cache-poisoning remote code execution on the ansible controller",
  "vendor": "Red Hat",
  "product": "Red Hat Ceph Storage 5",
  "cvss": {
    "score": 8.1,
    "source": "cna",
    "vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "description": "A flaw was found in the memcached cache plugin of the community.general Ansible\ncollection. Although its documentation states that records are stored in JSON\nformat, the plugin performs no explicit serialization and relies on\npython-memcached, which pickles values on write and unpickles them on read.\nBecause memcached is unauthenticated and cache keys are predictable, an attacker\nable to reach a network-exposed or shared memcached instance can write a crafted\npickle payload that is deserialized and executed on the Ansible controller when\nthe poisoned fact cache is next read, leading to remote code execution.",
  "cwe": "CWE-502",
  "cvss_by_source": {
    "cna": 8.1
  },
  "repos": [],
  "remediation": {
    "workarounds": [
      "Bind memcached to localhost only (the plugin default, 127.0.0.1:11211) and\n  never expose an unauthenticated memcached across a trust boundary; isolate the\n  cache to the controller. Prefer the redis cache plugin (explicit JSON) or the\n  jsonfile/yaml cache plugins where a shared/remote fact cache is required. Treat\n  any host with write access to the fact-cache memcached as trusted to run code\n  on the controller."
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
