# CVE-2025-0750: Cri-o: cri-o path traversal in log handling functions allows arbitrary unmounting

> An attacker with pod creation permissions can exploit path traversal in CRI-O log functions to unmount arbitrary host directories, causing node-level denial of service.

- **Severity:** Medium 6.6 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Jan 2025
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-110333, GHSA-hp5j-2585-qx6g, GO-2025-3426, RHSA-2025:1122

## What is CVE-2025-0750?

CVE-2025-0750 is a medium-severity path traversal vulnerability in Red Hat OpenShift Container Platform 4, published on 28 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in CRI-O. A path traversal issue in the log management functions (UnMountPodLogs and LinkContainerLogs) may allow an attacker with permissions to create and delete Pods to unmount arbitrary host paths, leading to node-level denial of service by unmounting critical system directories.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2025-0750?

3 open source packages ship an affected version, including github.com/cri-o/cri-o.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/cri-o/cri-o` | Go | All versions | None |
| `github.com/cri-o/cri-o` | Go | All versions to 1.33.0 | None |
| `github.com/cri-o/cri-o` | Go | All versions to 1.33.0 | None |
| `cri-o` | Red Hat:openshift:4.17::el8 | All versions | 0:1.30.10-3.rhaos4.17.gitd088fcf.el8 |
| `cri-o-debuginfo` | Red Hat:openshift:4.17::el8 | All versions | 0:1.30.10-3.rhaos4.17.gitd088fcf.el8 |
| `cri-o-debugsource` | Red Hat:openshift:4.17::el8 | All versions | 0:1.30.10-3.rhaos4.17.gitd088fcf.el8 |
| `cri-o` | Red Hat:openshift:4.17::el9 | All versions | 0:1.30.10-3.rhaos4.17.gitd088fcf.el9 |
| `cri-o-debuginfo` | Red Hat:openshift:4.17::el9 | All versions | 0:1.30.10-3.rhaos4.17.gitd088fcf.el9 |
| `cri-o-debugsource` | Red Hat:openshift:4.17::el9 | All versions | 0:1.30.10-3.rhaos4.17.gitd088fcf.el9 |

## How do I fix CVE-2025-0750?

Apply the vendor's patch.

## Is CVE-2025-0750 being exploited?

There is no known exploitation of CVE-2025-0750 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-0750 and fix it if it is affected.

What it is: CVE-2025-0750 is a medium-severity path traversal vulnerability in Red Hat OpenShift Container Platform 4, published on 28 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-0750 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/cri-o/cri-o (Go): affected all versions; no fix listed
- github.com/cri-o/cri-o (Go): affected all versions up to 1.33.0; no fix listed
- github.com/cri-o/cri-o (Go): affected all versions up to 1.33.0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-0750/ (Markdown: https://insights.sbomify.com/CVE-2025-0750/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-0750
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-0750
- OSV: https://osv.dev/vulnerability/CVE-2025-0750

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-0750/
Summaries are generated and may contain mistakes; the official description above is the record.