CVE-2026-113957: Apple container vulnerability
An attacker who controls the registry, a mirror, or the network path to it may be able to serve arbitrary image content in response to a pull by digest, so that a user runs an image other than the one they pinned. The fix compares the returned digest to the pinned digest and fails the pull on a mismatch. Tag pulls are exempt, because a tag is mutable by design. The fix also verifies the hash of manifests and blobs when they are fetched. This vulnerability is addressed in container version 1.6.0 and containerization version 0.52.1.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
containerto a version that resolves this vulnerability.Fixed in 1.6.0 - Upgrade
Upgrade
containerizationto a version that resolves this vulnerability.Fixed in 0.52.1
Event History
Frequently Asked Questions
Who is exposed to this issue?
Users of Apple container or Apple containerization who pull images by digest are exposed if an attacker controls the registry, a mirror, or the network path to the registry. Tag pulls are not covered by this issue because tags are mutable by design.
What must an attacker be able to do to exploit it?
The attacker must be able to serve content for an image pull by digest, such as through control of the registry or mirror or by intercepting the network path. They can then provide image content different from the digest-pinned image.
Which versions contain the fix?
The issue is addressed in container version 1.6.0 and containerization version 0.52.1. The fix rejects digest-pinned pulls when the returned digest does not match and verifies fetched manifests and blobs.