High [CVE-2026-19693] Arbitrary file write via symlink in archive
This high-severity Red Hat Linux advisory covers CVE-2026-19693 affecting Node HealthCheck Operator, OpenShift Pipelines, Red Hat Build of Podman Desktop.
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
extract-zip through 2.0.1 containment-checks only the parent directory of each archive entry and never the entry's own final path component, so an archive containing two entries with identical names - a symlink whose target is outside the destination, followed by a regular file - writes through the planted symlink and yields an arbitrary file write outside the destination directory.
By crafting a malicious zip archive containing a symbolic link (symlink) and a regular file with the same name, the attacker can bypass security checks. The extract-zip utility incorrectly validates only the parent directory, enabling the attacker to write files to arbitrary locations on the system.
The flaw arises from insufficient validation of archive entries, allowing a remote attacker to write files to arbitrary locations on the system by providing a specially crafted zip archive. This requires user interaction to extract the malicious archive, but successful exploitation could lead to significant system integrity and availability compromise.
Red Hat severity: Important — CVSS 8.1 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H). Weakness: CWE-59.
Affected products named by the advisory: Node HealthCheck Operator; OpenShift Pipelines; Red Hat Build of Podman Desktop; Red Hat Ceph Storage 4; and 6 more.
- 2.0.1
Official advisory · high-confidence parse· fetched 15 days ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.
Official advisory · high-confidence parse· fetched 15 days ago·verify at source
Mitigation checklist
- Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Official advisory · high-confidence parse· fetched 15 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.