CVE-2026-20613
Apple Containerization path traversal
- Published22 Jan 2026
Description
The ArchiveReader.extractContents() function used by cctl image load and container image load performs no pathname validation before extracting an archive member. This means that a carelessly or maliciously constructed archive can extract a file into any user-writable location on the system using relative pathnames. This issue is addressed in container 0.8.0 and containerization 0.21.0.
CVSS 3.1 breakdown
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HAffected products
Remediation
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-20613 being actively exploited?
CVE-2026-20613 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.28%.
How severe is CVE-2026-20613?
CVE-2026-20613 has a CVSS 3.1 base score of 7.8, rated high. EPSS estimates a 0.28% probability of exploitation.
Which products are affected by CVE-2026-20613?
Affected products include Apple Containerization, Apple Container.
How do I fix CVE-2026-20613?
Upgrade affected software to a fixed version, for example Apple Containerization 0.21.0, Apple Container 0.8.0 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-20613 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.