High [CVE-2026-17106] Arbitrary file write via link following in tar extraction
This high-severity Red Hat Linux advisory covers CVE-2026-17106 affecting Red Hat Enterprise Linux 10, Logging Subsystem for Red Hat OpenShift 6.6, Multicluster Global Hub 1.8.2.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Summary
The tar extraction routines in moby/go-archive (Unpack, UnpackLayer, Untar/UntarUncompressed, and the ApplyLayer helpers) do not confine filesystem operations to the destination directory.
The extractor decides where each archive entry lands using lexical string checks and then performs the filesystem operation on a path that is resolved by the OS, so links introduced by the archive can be followed out of the destination directory.
An attacker who controls the contents of an archive can create or overwrite files at arbitrary paths writable by the extracting process. This could lead to unauthorized modification of system files or potentially arbitrary code execution.
This Important severity vulnerability in `moby/go-archive` allows for arbitrary file writes during tar extraction.
An attacker providing a specially crafted tar archive can exploit symlink following to create or overwrite files outside the intended directory, potentially leading to system compromise in environments processing untrusted archives, such as container build systems. Red Hat severity: Important — CVSS 7.8 (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H).
Weakness: CWE-59.
Affected products named by the advisory: Red Hat Enterprise Linux 10; Logging Subsystem for Red Hat OpenShift 6.6; Multicluster Global Hub 1.8.2; Red Hat Advanced Cluster Management for Kubernetes 2.17; and 18 more.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 10 days ago·verify at source
- 29.7.0
- 5.4.0
- 0.38.0
- 0.3.0
- podman-7:5.8.2-9.el10_2
- rhel10/podman:7:5.8.2-9.el10_2
- ubi10/podman:7:5.8.2-9.el10_2
- podman-6:5.8.2-7.el9_8
- openshift-logging/cluster-logging-rhel9-operator:1788439505
- multicluster-globalhub/multicluster-globalhub-grafana-rhel9:1788441983
- multicluster-globalhub/multicluster-globalhub-grafana-rhel9:1790639009
- rhacm2/acm-grafana-rhel9:1790240693
- rhem/flightctl-alert-exporter-rhel10:1789485358
- rhem/flightctl-alertmanager-proxy-rhel10:1789485956
- rhem/flightctl-api-rhel10:1789485653
- rhem/flightctl-cli-artifacts-rhel10:1789486382
- rhem/flightctl-db-setup-rhel10:1789487147
- rhem/flightctl-imagebuilder-api-rhel10:1789485823
- rhem/flightctl-imagebuilder-worker-rhel10:1789485526
- rhem/flightctl-pam-issuer-rhel10:1789487060
- rhem/flightctl-periodic-rhel10:1789486651
- rhem/flightctl-telemetry-gateway-rhel10:1789486468
- rhem/flightctl-userinfo-proxy-rhel10:1789486659
- rhem/flightctl-worker-rhel10:1789486740
- rhem/flightctl-alert-exporter-rhel9:1789485374
- rhem/flightctl-alertmanager-proxy-rhel9:1789486471
- rhem/flightctl-api-rhel9:1789485317
- rhem/flightctl-cli-artifacts-rhel9:1789485390
- rhem/flightctl-db-setup-rhel9:1789485698
- rhem/flightctl-imagebuilder-api-rhel9:1789485260
- rhem/flightctl-imagebuilder-worker-rhel9:1789487407
- rhem/flightctl-pam-issuer-rhel9:1789487540
- rhem/flightctl-periodic-rhel9:1789485282
- rhem/flightctl-telemetry-gateway-rhel9:1789486233
- rhem/flightctl-userinfo-proxy-rhel9:1789485510
- rhem/flightctl-worker-rhel9:1789488061
- podman-main-6.0.2-2.2.hum1
- RHSA-2026:70201
- RHSA-2026:69961
- RHSA-2026:66521
- RHSA-2026:68515
- RHSA-2026:73038
- RHSA-2026:72879
- RHSA-2026:68006
- RHSA-2026:68254
- RHSA-2026:52807
Official advisory · high-confidence parse· fetched 10 days ago·verify at source
Mitigation checklist
- To mitigate this issue, avoid processing tar archives from untrusted sources. When handling archives from potentially untrusted origins, ensure that the extraction process is executed with the least privileges necessary to limit the impact of any arbitrary file write attempts.
Official advisory · high-confidence parse· fetched 10 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.