# CVE-2026-115424: Oc: oc: symlink/hardlink target validation bypass in oc image extract allows file write outside destination


- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Oct 2026
- **Updated:** 22 Oct 2026
- **Also known as:** GHSA-g35x-264p-5xp5

## What is CVE-2026-115424?

CVE-2026-115424 is a medium-severity vulnerability in Red Hat OpenShift Container Platform 4, published on 22 Oct 2026. 

### Official description

A flaw was found in the OpenShift client oc. When extracting container image layers with oc image extract, the application fails to properly sanitize symbolic and hard link targets pointing to absolute paths or to sibling directories of the extraction destination. An attacker who supplies a malicious container image can exploit this vulnerability by embedding links, and a chained file entry, that reference locations outside the intended extraction directory. This allows the attacker to write attacker-controlled content to arbitrary locations on the host filesystem with the privileges of the user running the command, potentially leading to file modification outside the destination directory.

Weakness: CWE-61 (UNIX Symbolic Link (Symlink) Following)

## Which versions are affected by CVE-2026-115424?


## How do I fix CVE-2026-115424?

No fix has been published for CVE-2026-115424 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-115424 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-115424 and fix it if it is affected.

What it is: CVE-2026-115424 is a medium-severity vulnerability in Red Hat OpenShift Container Platform 4, published on 22 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115424 in the wild and no public exploit code.

Affected product: Red Hat OpenShift Container Platform 4. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2026-115424/ (Markdown: https://insights.sbomify.com/CVE-2026-115424/index.md)
```

## Sources

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

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