There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - A vulnerability was found in CRI-O, where it can be requested to take a checkpoint archive of a container
    and later be asked to restore it. When it does that restoration, it attempts to restore the mounts from
    the restore archive instead of the pod request. As a result, the validations run on the pod spec,
    verifying that the pod has access to the mounts it specifies are not applicable to a restored container.
    This flaw allows a malicious user to trick CRI-O into restoring a pod that doesn't have access to host
    mounts. The user needs access to the kubelet or cri-o socket to call the restore endpoint and trigger the
    restore. (CVE-2024-8676)

The remote Red Hat Enterprise Linux CoreOS 4 host has a package installed that is affected by a vulnerability as referenced in the RHSA-2025:0648 advisory.

  - cri-o: Checkpoint restore can be triggered from different namespaces (CVE-2024-8676)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote Red Hat Enterprise Linux CoreOS 4 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2025:1908 advisory.

  - cri-o: Checkpoint restore can be triggered from different namespaces (CVE-2024-8676)

  - podman: buildah: Container breakout by using --jobs=2 and a race condition when building a malicious     Containerfile (CVE-2024-11218)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - A vulnerability was found in CRI-O, where it can be requested to take a checkpoint archive of a container     and later be asked to restore it. When it does that restoration, it attempts to restore the mounts from     the restore archive instead of the pod request. As a result, the validations run on the pod spec,     verifying that the pod has access to the mounts it specifies are not applicable to a restored container.
    This flaw allows a malicious user to trick CRI-O into restoring a pod that doesn't have access to host     mounts. The user needs access to the kubelet or cri-o socket to call the restore endpoint and trigger the     restore. (CVE-2024-8676)

Note that Nessus relies on the presence of the package as reported by the vendor.

The remote Redhat Enterprise Linux 8 / 9 host has a package installed that is affected by a vulnerability as referenced in the RHSA-2025:0648 advisory.

    Red Hat OpenShift Container Platform is Red Hat's cloud computing Kubernetes application platform solution     designed for on-premise or private cloud deployments.

    This advisory contains the RPM packages for Red Hat OpenShift Container Platform 4.15.44. See the     following advisory for the container images for this release:

    https://access.redhat.com/errata/RHSA-2025:0646

    Security Fix(es):

    * cri-o: Checkpoint restore can be triggered from different namespaces     (CVE-2024-8676)

    All OpenShift Container Platform 4.15 users are advised to upgrade to these updated packages and images     when they are available in the appropriate release channel. To check for available updates, use the     OpenShift CLI (oc) or web console. Instructions for upgrading a cluster are available at     https://docs.openshift.com/container-platform/4.15/updating/updating_a_cluster/updating-cluster-cli.html

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The version of Tencent Linux installed on the remote TencentOS Server 4 host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the TSSA-2025:0033 advisory.

    Package updates are available for TencentOS Server 4 that fix the following vulnerabilities:

    CVE-2024-8676:
    A vulnerability was found in CRI-O, where it can be requested to take a checkpoint archive of a container     and later be asked to restore it. When it does that restoration, it attempts to restore the mounts from     the restore archive instead of the pod request. As a result, the validations run on the pod spec,     verifying that the pod has access to the mounts it specifies are not applicable to a restored container.
    This flaw allows a malicious user to trick CRI-O into restoring a pod that doesn't have access to host     mounts. The user needs access to the kubelet or cri-o socket to call the restore endpoint and trigger the     restore.

Tenable has extracted the preceding description block directly from the Tencent Linux security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote Redhat Enterprise Linux 8 / 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2025:1908 advisory.

    Red Hat OpenShift Container Platform is Red Hat's cloud computing Kubernetes application platform solution     designed for on-premise or private cloud deployments.

    This advisory contains the RPM packages for Red Hat OpenShift Container Platform 4.18.2. See the following     advisory for the container images for this release:

    https://access.redhat.com/errata/RHBA-2025:1904

    Security Fix(es):

    * podman: buildah: Container breakout by using --jobs=2 and a race     condition when building a malicious Containerfile (CVE-2024-11218)
    * cri-o: Checkpoint restore can be triggered from different namespaces     (CVE-2024-8676)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

    All OpenShift Container Platform 4.18 users are advised to upgrade to these updated packages and images     when they are available in the appropriate release channel. To check for available updates, use the     OpenShift CLI (oc) or web console. Instructions for upgrading a cluster are available at     https://docs.openshift.com/container-platform/4.18/updating/updating_a_cluster/updating-cluster-cli.html

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Published	Updated	Severity
412170	SCA: security update for github.com/cri-o/cri-o (GHSA-7p9f-6x8j-gxxp)	Tenable Cloud Security	SCA Checks	1/23/2025	7/2/2026	critical
412170	SCA: security update for github.com/cri-o/cri-o (GHSA-7p9f-6x8j-gxxp)	Tenable Self-Hosted Container Security	SCA Checks	1/23/2025	7/2/2026	critical
311895	RHCOS 4 : OpenShift Container Platform 4.15.44 (RHSA-2025:0648)	Nessus	Red Hat Local Security Checks	5/4/2026	5/4/2026	critical
311877	RHCOS 4 : OpenShift Container Platform 4.18.2 (RHSA-2025:1908)	Nessus	Red Hat Local Security Checks	5/4/2026	5/4/2026	critical
230421	Linux Distros Unpatched Vulnerability : CVE-2024-8676	Nessus	Misc.	3/6/2025	5/18/2026	high
214789	RHEL 8 / 9 : OpenShift Container Platform 4.15.44 (RHSA-2025:0648)	Nessus	Red Hat Local Security Checks	1/29/2025	6/5/2025	critical
238683	TencentOS Server 4: cri-o (TSSA-2025:0033)	Nessus	Tencent Local Security Checks	6/16/2025	12/4/2025	critical
228831	RHEL 8 / 9 : OpenShift Container Platform 4.18.2 (RHSA-2025:1908)	Nessus	Red Hat Local Security Checks	3/5/2025	6/5/2025	critical

Detections

Analytics

Plugins Search

critical

critical

critical

critical

high

critical

critical

critical