CVE-2026-105769 with a CVSS score of 9.3 is a critical improper authentication and credential exposure flaw in the kaniko Azure Container Registry credential helper, affecting kaniko before v1.25.20. The helper uses an unanchored regular expression to identify Azure Container Registry hosts, so any hostname containing .azurecr.io, .azurecr.cn, .azurecr.de, or .azurecr.us is treated as a legitimate registry. An attacker who can influence a Dockerfile or build arguments, such as a FROM line or COPY --from image reference, can direct kaniko to a lookalike registry host without requiring a RUN instruction or push. When Azure identity material is available through environment service principal credentials, federated workload identity tokens, or managed identity endpoints, kaniko requests credentials before contacting the registry and sends a live Azure Resource Manager access token to the attacker-controlled host in an Authorization header and form field. The attacker can then use the token against Azure Resource Manager with the identity's role assignments or exchange it at real Azure Container Registry endpoints to obtain registry credentials, potentially pushing images if the identity has sufficient permissions. This can expose cloud infrastructure, secrets, and build pipelines to unauthorized access and supply-chain compromise.
We recommend you to update kaniko to version 1.25.20.[/subscribe_to_unlock_form]
CVE-2026-105769 with a CVSS score of 9.3 is a critical improper authentication and credential exposure flaw in the kaniko Azure Container Registry credential helper, affecting kaniko before v1.25.20. The helper uses an unanchored regular expression to identify Azure Container Registry hosts, so any hostname containing .azurecr.io, .azurecr.cn, .azurecr.de, or .azurecr.us is treated as a legitimate registry. An attacker who can influence a Dockerfile or build arguments, such as a FROM line or COPY --from image reference, can direct kaniko to a lookalike registry host without requiring a RUN instruction or push. When Azure identity material is available through environment service principal credentials, federated workload identity tokens, or managed identity endpoints, kaniko requests credentials before contacting the registry and sends a live Azure Resource Manager access token to the attacker-controlled host in an Authorization header and form field. The attacker can then use the token against Azure Resource Manager with the identity's role assignments or exchange it at real Azure Container Registry endpoints to obtain registry credentials, potentially pushing images if the identity has sufficient permissions. This can expose cloud infrastructure, secrets, and build pipelines to unauthorized access and supply-chain compromise.
We recommend you to update kaniko to version 1.25.20.[emaillocker id="1283"]
The following reports contain further technical details:
[/emaillocker]