cve.bz

CVE-2026-107174 Source-to-image: source-to-image: security boundary bypass via absolute symbolic link extraction

6.4 mediumEPSS 0.3%

Medium (6.4) in red hat. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
A flaw was found in source-to-image. When unpacking archive files, the application fails to properly sanitize symbolic links pointing to absolute file paths. An attacker who supplies a malicious builder image can exploit this vulnerability by embedding links pointing outside the extraction directory. This allows the attacker to bypass sandbox boundaries, potentially leading to unauthorized information disclosure or file modification on the host system.

Severity

CVSS 3.1

6.4 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 21st percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-07. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-61 UNIX Symbolic Link (Symlink) Following
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
Assigned by
redhat (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-107174 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-107174?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-107174?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-107174 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • red hat:openshift serverless
  • red hat:openshift source-to-image (s2i)
  • red hat:red hat openshift container platform 4
  • red hat:red hat openshift container platform 5
  • red hat:red hat web terminal

Versions

From the CNA's record in the CVE List.

ProductAffected
source-to-imagethrough 1.6.4

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A flaw was found in the source-to-image (s2i) tool used during container image builds. When s2i extracts a tar archive in its restricted ("paranoid") mode, symlink entries are validated using a computed path, but the symlink is still created using the raw target from the archive. If that target is an absolute path, the check can succeed while the symlink on disk points outside the intended extraction directory. This weakens the containment that was introduced for an earlier tar extraction issue (CVE-2018-1103).

An attacker who can supply or influence the tar content used during an s2i build (for example through a malicious or compromised builder image or build scripts such as assemble or save-artifacts) may cause symlinks to be written that reference arbitrary locations on the build host filesystem. Further impact depends on whether later build steps follow those symlinks.

This issue affects Red Hat offerings that ship or embed source-to-image for builds, including Red Hat OpenShift Container Platform 4.12 through 4.22, the source-to-image container images, and select related products identified in this flaw record.

Red Hat is evaluating fixes for affected products. Customers should only use trusted builder images and trusted application source for s2i-based builds until an updated source-to-image version is available in their environment.

Red Hat's mitigation

Treat s2i builder images and application source as trusted inputs. Do not run s2i-based builds against builder images or repositories you do not control or have not verified.

Where possible, run builds on isolated build nodes and restrict who can trigger builds or change BuildConfig and image stream references that point at custom builder images.

There is no configuration option to disable only this symlink extraction behavior without changing how builds are performed. Apply updated source-to-image packages or rebuilt platform images when Red Hat publishes them for your product and stream.

ProductPackageStateAdvisory
OpenShift Serverlessopenshift-serverless-1/kn-client-kn-rhel9Fix deferred
OpenShift Serverlessopenshift-serverless-1/kn-plugin-func-func-util-rhel9Fix deferred
OpenShift Serverlessopenshift-serverless-clientsFix deferred
OpenShift Source-to-Image (S2I)source-to-image/source-to-image-rhel8Fix deferred
OpenShift Source-to-Image (S2I)source-to-image/source-to-image-rhel9Fix deferred
Red Hat OpenShift Container Platform 4openshift4/ose-docker-builderFix deferred
Red Hat OpenShift Container Platform 4openshift4/ose-docker-builder-rhel9Fix deferred
Red Hat Web Terminalweb-terminal/web-terminal-tooling-rhel9Fix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-107174.

Attack patterns (CAPEC)

  • CAPEC-27 Leveraging Race Conditions via Symbolic Links Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON