LiveActive security incident?Get immediate response
CVE Record

CVE-2026-20613: The ArchiveReader.extractContents() function used by cctl image load and container image load performs no p...

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.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-20613 is a path traversal flaw in Apple Container and Containerization archive extraction. If a user loads a malicious or careless container image archive, files may be written to user-writable locations outside the intended extraction path. This can affect confidentiality, integrity, and availability on the local system.

Executive priority

Prioritize remediation for developer machines, CI systems, and build hosts that handle external container image archives. Business urgency is high where untrusted images are routinely imported.

Technical view

ArchiveReader.extractContents(), used by cctl image load and container image load, did not validate archive member pathnames before extraction. Relative pathnames could cause writes to arbitrary user-writable locations. The issue is classified as CWE-22 and is addressed in container 0.8.0 and containerization 0.21.0.

Likely exposure

Exposure is mainly local developer or build environments where Apple Container or Containerization load container image archives. Systems processing untrusted or externally supplied image archives are at higher risk.

Exploitation context

The CVSS vector indicates local access, low complexity, no privileges, and required user interaction. The provided sources do not report active exploitation, and the CVE is not marked KEV.

Researcher notes

Evidence is limited to the CVE record and Apple advisory. The bug is a pathname validation failure during archive extraction, not a remotely reachable network service issue based on the supplied CVSS vector.

Mitigation direction

  • Upgrade Apple container to 0.8.0 or later.
  • Upgrade Apple containerization to 0.21.0 or later.
  • Avoid loading untrusted container image archives until updated.
  • Review Apple’s GitHub advisory for any additional vendor guidance.

Validation and detection

  • Inventory systems using Apple Container or Containerization.
  • Confirm installed versions meet the fixed releases.
  • Identify workflows that load third-party or user-supplied image archives.
  • Review recent image-load activity where untrusted archives were processed.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-22: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Container behavior lookup

The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-20613 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H1.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2026-20613Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
AppleContainerunspecifiedListed
AppleContainerizationunspecifiedListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-22 · source CWE mapping

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.