Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By redhat

  2. Published

  3. · 11 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-115424, by who scored it
Scored byCVSSScoreVector
redhatCNA (assigner)3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
NVDNVD · Awaiting Analysis3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
EPSS (exploitation in 30 days)
0.16% · top 94% of all CVEs (20 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

What to do

Workaround: Treat container images as trusted inputs when using oc image extract. Do not extract images from registries or publishers you do not control or have not verified. Where possible, run oc image extract as an unprivileged user and into a dedicated, isolated destination directory, and avoid fixed/predictable destination paths in automated or CI pipelines. Restrict who can modify the image references that automated extraction jobs consume. There is no configuration option to disable only this link-extraction behavior. Apply updated oc client packages or rebuilt platform images when Red Hat publishes them for your product and stream.

References

References2

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-115424 badge
[![CVE-2026-115424](https://cveledger.app/badge/CVE-2026-115424.svg)](https://cveledger.app/cve/CVE-2026-115424)

Record last updated .