NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
HIGH severity

CVE-2024-5154 — cri-o

HIGH

CVE-2024-5154 is a high-severity (CVSS 8.1) Path Traversal vulnerability in github.com/cri-o/cri-o. A fix is available for github.com/cri-o/cri-o — see the affected versions and patch details below.

Cri-o: malicious container can create symlink on host

Also known asGHSA-j9hf-98c3-wrm8GO-2024-2919
Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed
Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • A successful exploit gives an attacker total control of the affected component, not partial access.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-5154.

EPSS Exploitation Probability

via FIRST.org ↗
1.2%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs69th percentile — riskier than 69% of all scored CVEsHighest risk
0.74%1.23%1.72%2.21%1.7%1.2%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected
🐹github.com/cri-o/cri-o🐹github.com/cri-o/cri-o🐹github.com/cri-o/cri-o

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Impact

A malicious container can affect the host by taking advantage of code cri-o added to show the container mounts on the host.

A workload built from this Dockerfile:

FROM docker.io/library/busybox as source
RUN mkdir /extra && cd /extra && ln -s ../../../../../../../../root etc

FROM scratch

COPY --from=source /bin /bin
COPY --from=source /lib /lib
COPY --from=source /extra .

and this container config:

{
  "metadata": {
      "name": "busybox"
  },
  "image":{
      "image": "localhost/test"
  },
  "command": [
      "/bin/true"
  ],
  "linux": {
  }
}

and this sandbox config

{
  "metadata": {
    "name": "test-sandbox",
    "namespace": "default",
    "attempt": 1,
    "uid": "edishd83djaideaduwk28bcsb"
  },
  "linux": {
    "security_context": {
      "namespace_options": {
        "network": 2
      }
    }
  }
}

will create a file on host /host/mtab

Patches

1.30.1, 1.29.5, 1.28.7

Workarounds

Unfortunately not

References

Are there any links users can visit to find out more?

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/cri-o/cri-o≥ 1.28.6&&< 1.28.71.28.7go get github.com/cri-o/cri-o@v1.28.7
🐹Gogithub.com/cri-o/cri-o≥ 1.29.4&&< 1.29.51.29.5go get github.com/cri-o/cri-o@v1.29.5
🐹Gogithub.com/cri-o/cri-o≥ 1.30.0&&< 1.30.11.30.1go get github.com/cri-o/cri-o@v1.30.1

Affected Products

2 products · 9 configurations
Application
cri-okubernetes
3 versions
1.28.61.29.41.30.0
Application
openshift container platformredhat
6 versions
3.114.04.124.134.144.15

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/cri-o/cri-o, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update github.com/cri-o/cri-o to 1.28.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-5154 is resolved across your whole dependency graph.

  3. Workarounds

    Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Red Hat OpenShift Container Platform (OCP) includes the vulnerable cri-o library, however it does not load untrusted container, therefore impact is reduced to Important.

ProductFixed inAdvisory
Red Hat OpenShift Container Platform 4.12cri-o-0:1.25.5-21.2.rhaos4.12.gita3eb75f.el8RHSA-2024:4008
Red Hat OpenShift Container Platform 4.13cri-o-0:1.26.5-18.2.rhaos4.13.git2e90133.el8RHSA-2024:4486
Red Hat OpenShift Container Platform 4.14cri-o-0:1.27.7-3.rhaos4.14.git674563e.el8RHSA-2024:3700
Red Hat OpenShift Container Platform 4.15cri-o-0:1.28.7-2.rhaos4.15.git111aec5.el8RHSA-2024:3676
Red Hat OpenShift Container Platform 4.16cri-o-0:1.29.5-7.rhaos4.16.git7db4ada.el8RHSA-2024:4159
Red Hat OpenShift Container Platform 4.17openshift/ose-rhel-coreos-9:417.94.202412040832-0RHSA-2024:10818

Frequently Asked Questions

### Impact A malicious container can affect the host by taking advantage of code cri-o added to show the container mounts on the host. A workload built from this Dockerfile: ``` FROM docker.io/library/busybox as source RUN mkdir /extra && cd /extra && ln -s ../../../../../../../../root etc FROM scratch COPY --from=source /bin /bin COPY --from=source /lib /lib COPY --from=source /extra . ``` and this container config: ``` { "metadata": { "name": "busybox" }, "image":{ "image": "localhost/test" }, "command": [ "/bin/true" ], "linux": { } } ``` and this s
O3 Security · Impact-Aware SCA

Is CVE-2024-5154 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2024-5154: cri-o — Fixed in 1.28.7