GHSA-PG57-6JWG-Q645
Containerd has image-pull DoS via crafted OCI index graph amplification
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Remediación | Parche v2.0.13 | github.com/containerd/containerd/v2 · -1 d desde divulgación | |
| Remediación | Parche v2.2.9 | github.com/containerd/containerd/v2 · -1 d desde divulgación | |
| Remediación | Parche v2.3.6 | github.com/containerd/containerd/v2 · -1 d desde divulgación | |
| Remediación | Parche v2.4.1 | github.com/containerd/containerd/v2 · -1 d desde divulgación | |
| Remediación | Parche v1.7.36 | github.com/containerd/containerd · -1 d desde divulgación | |
| Divulgación | Publicada | GHSA-PG57-6JWG-Q645 divulgada | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Detectada | Ingresó al índice |
Impact
A vulnerability exists in containerd's image pull handlers where a crafted OCI image index containing deeply nested or heavily fanned-out descriptor graphs can cause unbounded CPU and memory consumption. During the `PullImage` operation, the recursive traversal and processing of child descriptors lack sufficient depth and breadth limits, and fail to adequately deduplicate identical descriptors. This unbounded traversal leads to excessive resource allocation.
Consequently, pulling a malicious image reference can result in prolonged stalls during container creation and significant resource pressure on the host system. This issue occurs entirely during the image pull phase, prior to any container execution.
Patches
This bug has been fixed in containerd 2.4.1, 2.3.6, 2.2.9, 2.0.13, and 1.7.36. Users should update to these versions to resolve the issue.
Workarounds
There are no known workarounds for this issue. Users are advised to only pull trusted images from known registries until the patch can be applied.
Credits
The containerd project would like to thank Jakub Ciolek at ElevenLabs and @jlgore who independently discovered and responsibly disclosed this issue in accordance with the containerd security policy https://github.com/containerd/project/blob/main/SECURITY.md.
For more information
If you have any questions or comments about this advisory:
- Open an issue in containerd
https://github.com/containerd/containerd/issues/new/choose - Email us at [security@containerd.io](mailto:security@containerd.io)
To report a security issue in containerd:
* Report a new vulnerability https://github.com/containerd/containerd/security/advisories/new
* Email us at [security@containerd.io](mailto:security@containerd.io)
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
gogithub.com/containerd/containerd/v2 |
Corregida | v2.0.13, v2.2.9, v2.3.6, v2.4.1 | -1 d · -1 d · -1 d · -1 d | v2.4.2 no afectada |
gogithub.com/containerd/containerd |
Corregida | v1.7.36 | -1 d | v1.7.36 no afectada |
1.7.36v1.7.362.0.13v2.0.132.2.9v2.2.92.3.6v2.3.62.4.1v2.4.1Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://nvd.nist.gov/vuln/detail/CVE-2026-53493https://github.com/containerd/containerd/security/advisories/GHSA-pg57-6jwg-q645https://github.com/containerd/containerd/commit/4f5f32636d47f051751065cf824a10da70c619fehttps://github.com/containerd/containerd/commit/94e83c14c8aac963e24e28105dab9c9af812a2a8https://github.com/containerd/containerdhttps://github.com/containerd/containerd/releases/tag/v1.7.36https://github.com/containerd/containerd/releases/tag/v2.0.13https://github.com/containerd/containerd/releases/tag/v2.2.9https://github.com/containerd/containerd/releases/tag/v2.3.6https://github.com/containerd/containerd/releases/tag/v2.4.1Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
