live wire
▸AI · Red Hat documents usage-based admission fair sharing for Kueue 1.4 on OpenShiftRed Hat Developer▸AI: Red Hat maps governed firewall changes from ServiceNow through Ansible and two human approval gatesRed Hat Developer▸CLUSTER MGMT · ACM 2.17 makes Submariner 0.24 GA with Important-rated fixesRed Hat Errata▸PLATFORM · Red Hat makes on-premises Lightspeed recommendations GA for Satellite 6.18Red Hat Errata▸SECURITY · Red Hat Hardened Images updates Tomcat 10 for nine authentication, access-control and DoS flawsRed Hat Errata▸AI · Open Data Hub 3.6.0 EA1 bundles Trainer, MLflow and llm-d componentsOpen Data Hub▸AI · Speculators 0.6.0 adds P-EAGLE parallel drafting for vLLM speculative decodingRed Hat Developer▸SECURITY · OpenShift 4.17.57 fixes seven Go and TLS CVEs in an Important-rated updateRed Hat Errata▸AI · Red Hat benchmarks local LLM guardrails with EvalHub, exposing regex accuracy and latency trade-offsRed Hat Developer▸AI · Red Hat maps silent tool-call failures across agentic pipelinesRed Hat▸API · Kuadrant 1.5.3 adds GRPCRoute policies and developer-portal API-key workflowsKuadrant▸AI · (Aug 25) IBM releases Apache-2.0 Granite 4.2 reasoning models in 3B, 8B and 30B sizesIBM Research▸JAVA · Red Hat build of Quarkus 3.33.3.SP1 fixes 13 CVEs in an Important-rated updateRed Hat errata▸AI · vLLM moves Kimi K2 RL weight sync across 384 H100s in 7.53 seconds (Aug 22)vLLM▸AI · Red Hat documents usage-based admission fair sharing for Kueue 1.4 on OpenShiftRed Hat Developer▸AI: Red Hat maps governed firewall changes from ServiceNow through Ansible and two human approval gatesRed Hat Developer▸CLUSTER MGMT · ACM 2.17 makes Submariner 0.24 GA with Important-rated fixesRed Hat Errata▸PLATFORM · Red Hat makes on-premises Lightspeed recommendations GA for Satellite 6.18Red Hat Errata▸SECURITY · Red Hat Hardened Images updates Tomcat 10 for nine authentication, access-control and DoS flawsRed Hat Errata▸AI · Open Data Hub 3.6.0 EA1 bundles Trainer, MLflow and llm-d componentsOpen Data Hub▸AI · Speculators 0.6.0 adds P-EAGLE parallel drafting for vLLM speculative decodingRed Hat Developer▸SECURITY · OpenShift 4.17.57 fixes seven Go and TLS CVEs in an Important-rated updateRed Hat Errata▸AI · Red Hat benchmarks local LLM guardrails with EvalHub, exposing regex accuracy and latency trade-offsRed Hat Developer▸AI · Red Hat maps silent tool-call failures across agentic pipelinesRed Hat▸API · Kuadrant 1.5.3 adds GRPCRoute policies and developer-portal API-key workflowsKuadrant▸AI · (Aug 25) IBM releases Apache-2.0 Granite 4.2 reasoning models in 3B, 8B and 30B sizesIBM Research▸JAVA · Red Hat build of Quarkus 3.33.3.SP1 fixes 13 CVEs in an Important-rated updateRed Hat errata▸AI · vLLM moves Kimi K2 RL weight sync across 384 H100s in 7.53 seconds (Aug 22)vLLM
upstreambeat.ai
releaseSECURITY

Podman 6.1.1 closes a tar extraction escape in archive workflows

A crafted archive can redirect extraction through malicious links and overwrite files outside the chosen directory with the extractor’s permissions.

Podman 6.1.1 fixes CVE-2026-17106
AI-generated illustration
By The News Desk· Sep 3, 2026the quick take — two AI hosts, this story only

Podman 6.1.1 addresses a high-severity path-traversal flaw in its archive-handling dependency that can let a crafted tar file escape the directory where an operator intended to unpack it. The release, published Sept. 2, names CVE-2026-17106 as its security fix and points operators to the underlying moby/go-archive advisory.

What the flaw does

The affected archive routines include Unpack, UnpackLayer, Untar, UntarUncompressed and the ApplyLayer helpers. According to the advisory, they used lexical string checks to decide whether an archive entry stayed under the destination directory. The operating system then resolved the actual filesystem path, including links created by the archive.

That gap means an attacker-controlled tar archive can introduce a malicious link and make a later extraction operation follow it beyond the destination. The result is not merely an unexpected filename inside an unpack directory: the extracting process can create or overwrite arbitrary files anywhere it already has permission to write.

GitHub’s reviewed advisory rates the issue High and reports a CVSS 4.0 base score of 7.1 with the vector CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N. In practical terms, exploitation requires hostile archive content to reach an extraction workflow; the damage is bounded by the privileges of the process performing that extraction.

Who needs to act

Operators should prioritize environments where Podman imports, copies, builds from or otherwise processes archives supplied by tenants, CI jobs or other partially trusted sources. Rootful automation has the larger potential blast radius because the extractor may be able to overwrite privileged host paths. Rootless execution limits writable locations, but it does not make the archive safe: files owned by the invoking user can still be targeted.

GitHub’s reviewed advisory lists every github.com/moby/go-archive version below 0.3.0 as vulnerable and 0.3.0 as the first patched version. Podman identifies 6.1.1 as the release carrying its fix. Podman 6.1.1 also repairs a separate dual-stack rootlessport regression affecting Podman Machine on WSL, but that bugfix is not part of the security issue.

Upgrade decision

Podman operators on the 6.1 line should move to 6.1.1 rather than relying on destination-path checks around untrusted tar files. Where Podman is supplied by a Linux distribution or enterprise product, the relevant decision point is the vendor package containing the backported fix, not the upstream version string alone; confirm the advisory or package changelog before assuming an older-looking build remains vulnerable.

If an upgrade cannot be deployed immediately, the upstream workaround is narrow: extract only trusted archives. Pipelines should stop accepting user-controlled tar input on affected workers, quarantine archives before extraction, and avoid running archive-processing steps with broader filesystem permissions than they need.

sources

Filed by The News Desk. Corrections: desk@upstreambeat.ai · Our standards →

comments · 0

    Comments are moderated before they appear. Your email is used once to confirm it is you — never shown, never sold. Corrections and questions get an answer from the desk when we have one.

    more from the desk