Database/Control plane, storage & DevOps
ansible-runner: streamed archive extraction follows symlinks and writes outside the target directory
Impact
The worker side of ansible-runner's transmit/worker protocol unpacks a streamed zip archive without validating symlink targets or member paths, and then applies chmod() and utime() to those unsanitized paths. A crafted archive can create files, plant symlinks, or change permissions anywhere the worker process can write - which Red Hat's assessment says can be leveraged toward code execution. On a GPU fleet this matters because ansible-runner workers are the thing that configures nodes: a worker that consumes attacker-influenced input can be turned into a foothold on the automation path that drives driver installs, firmware pushes and node provisioning across the whole fleet. Integrity impact, not confidentiality, per the record.
Who can reach it
An actor who can influence the archive content a worker consumes over the transmit/worker protocol. The record's vector is network with low privileges required and high attack complexity, so it needs an existing authenticated position that feeds jobs into a worker rather than anonymous reachability.
What to do
Track the upstream fix in ansible-runner PR #1550 and the Red Hat Ansible Automation Platform 2 errata; the record names no fixed version, so apply the vendor update when it ships. In the meantime, treat worker nodes as trusting their job source: do not let untrusted parties submit transmit payloads, and run workers as unprivileged users in constrained containers so an escaped write lands somewhere harmless. The fix is a package update to the automation controller and its workers, not a node-level change.
References
Related entries
- GitLab EE: upstream repository owner can poison cached Maven packages of other upstreams in a virtual registryCVE-2026-112203 · GitLab EE (Maven virtual registry)Medium
- nfs-utils rpc.statd: memory leak on state notification requests lets a remote attacker exhaust node memoryCVE-2026-89096 · nfs-utils rpc.statd (NSM state notification callback handling)Medium
- HashiCorp Vault: new uninitialized node can be tricked into sending its server credentials to an attackerCVE-2026-92735 · HashiCorp Vault / Vault Enterprise (integrated storage Raft join)Medium
- GitLab CE/EE: Pages path validation flaw exposes private CI/CD job artifacts of other projectsCVE-2026-11768 · GitLab CE/EE (GitLab Pages artifact serving)Medium
- GitLab: improper redirect validation in the Kubernetes proxy sends cluster auth tokens to an attacker-chosen serverCVE-2026-7767 · GitLab CE/EE (Kubernetes agent proxy redirect validation)Medium
- DMTF libspdm - SPDM Requester timeout handling: A libspdm Requester stores the Responder's CTExponentCVE-2023-32690 · DMTF libspdm - SPDM Requester timeout handlingMedium
This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.