Live › vulnerability › CVE-2026-113957
Go to dashboardWhen a pull is made by digest, an attacker who controls the registry, a mirror, or the network path can serve other image content, so the user runs an image other than the one they pinned. The fix compares the returned digest to the pinned digest, fails on a mismatch, and verifies manifest and blob hashes when they are fetched.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-29 01:36 UTC. All times on this page are UTC.
Teams that pull images by digest through a registry, mirror, or network path they do not fully control are exposed to a substituted image. The sources do not say which configurations make this more likely. Tag-only pulls are exempt by design, since tags are mutable.
No product ranges from the sources yet.
container version is below 1.6.0.containerization version is below 0.52.1.container to 1.6.0 or later.containerization to 0.52.1 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-113957")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.