CVE-2026-5317: Untrusted tar header in OCI layer extraction causes DoS (Medium)

Vulnerability Summary: Memory Allocation Issue Caused by Untrusted Tar Header During OCI Layer Extraction Vulnerability Overview Title: Oci layer extraction allocates from untrusted tar header CVE ID: CVE-2026-5317 Severity: Medium (CVSS v3.1 score 6.5/10) Vulnerability Type: Memory allocation issue caused by untrusted input Description: At , the call uses the field from an untrusted tar header. An attacker can trigger large memory allocations by controlling the tar header (512-byte tar header, including the field encoded as ) returned by the OCI registry. This leads to an unrecoverable OOM in the Go runtime, causing a crash loop in the shared controller and resulting in a cluster-wide DoS triggered by a single request. Impact Scope Affected Versions: < 1.7.3, < 1.8.1 Fixed Versions: 1.7.4, 1.8.1 Affected Component: Gateway (Envoy) Attack Vector: Network Attack Complexity: Low Required Privileges: Low User Interaction: None Scope: Unchanged Confidentiality/Integrity: No impact Availability: High impact Resolution Upgrade to version 1.7.4 or 1.8.1 Fix method: Validate or constrain from the tar header to prevent untrusted input from being directly used for memory allocation Prerequisites Tenant can create an (baseline) Controller can escape to an attacker-controlled OCI registry No registry allowlist (no related checks in the code) The layer is presented with a Docker/OCI media type POC / Exploit Code No POC code or exploit code block is included in the screenshot.

Goal Reached Thanks to every supporter — we hit 100%!

CVE-2026-5317: Untrusted tar header in OCI layer extraction causes DoS (Medium)

More from this source