Skip to main content
VulnerabilityPublished Updated

CVE-2024-8676: cri-o · Improper Authorization

Affects cri-oSource GCVE Database

0
Compare

Not known to be exploited · CVSS 7.4 High.

Data as of 5 Nov 2026, 15:34 UTC

CVSS 3.1 base score
7.4High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (redhat)CVSS 3.17.4
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Nov 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
cri-oAffected
  • =0
  • =1.30.0
  • =1.31.0
Fixed in–

AI-suggested

Red Hat has released updated packages for OpenShift Container Platform 4.16.26 that address this vulnerability. Users should upgrade to these updated packages and images as soon as they are available via the appropriate release channels. Instructions for upgrading clusters are provided by Red Hat. No alternative mitigations or workarounds are indicated in the advisory.

Description

CVE-2024-8676 is a high-severity vulnerability in CRI-O where improper authorization allows a user with access to the kubelet or CRI-O socket to restore a container checkpoint with mounts not authorized for the pod. This occurs because CRI-O restores mounts from the checkpoint archive without validating them against the pod's current mount permissions, bypassing normal access controls.

References

Community reviews

Loading reviews…