{
  "id": "CVE-2026-62146",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-62146",
  "published_at": "2026-09-30T11:49:20.363Z",
  "title": "Cri-o: cri-o: sandbox state poisoning via pod annotations may expose runtime socket",
  "vendor": "Red Hat",
  "product": "Red Hat OpenShift Container Platform 4.16",
  "cvss": {
    "score": 7.8,
    "source": "cna",
    "vector": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/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 trust-boundary flaw in CRI-O's sandbox state persistence allows attacker-influenced pod metadata to overwrite CRI-O's own reserved sandbox bookkeeping; once reloaded as trusted after a restart, a later container recreate in that sandbox can expose a host-side runtime-management resource inside the container, enabling container escape.",
  "cwe": "CWE-501",
  "cvss_by_source": {
    "cna": 7.8
  },
  "repos": [
    {
      "repo": "TeamN4C/SG-2026-0026",
      "url": "https://github.com/TeamN4C/SG-2026-0026",
      "created_at": "2026-10-01T12:08:26Z",
      "first_seen_at": "2026-11-14T14:50:35.824Z",
      "stars": 0,
      "is_poc": "unknown",
      "suspicion_score": 15,
      "suspicious": false,
      "suspicion_reasons": [
        "no network code found (normal for a local exploit)"
      ],
      "status": "analyzed",
      "owner_created_at": "2026-06-19T14:05:19Z"
    }
  ],
  "remediation": {
    "affected": [
      {
        "vendor": "Red Hat",
        "product": "Red Hat OpenShift Container Platform 4.16",
        "ranges": null,
        "fixed_in": [
          "0:1.29.13-16.rhaos4.16.git84cfdc6.el8"
        ]
      }
    ],
    "upgrade": [
      "Upgrade Red Hat OpenShift Container Platform 4.16 to 0:1.29.13-16.rhaos4.16.git84cfdc6.el8 or later."
    ],
    "workarounds": [
      "There is no complete workaround; until a fix is available, administrators should restrict who can create/update pods and set arbitrary annotations via RBAC/admission policy, minimize unnecessary CRI-O restarts or node reboots and monitor for anomalous container mounts (e.g. under /dev/shm) following runtime restarts, then apply the vendor patch once released."
    ],
    "references": [
      {
        "kind": "Vendor advisory",
        "url": "https://access.redhat.com/errata/RHSA-2026:89713"
      },
      {
        "kind": "Vendor advisory",
        "url": "https://github.com/cri-o/cri-o/security/advisories/GHSA-6wmc-5877-hgc9"
      }
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
