Live › vulnerability › CVE-2026-105769
kaniko before 1.25.20 sends a Microsoft Entra ID access token for Azure Resource Manager to any registry host whose name contains .azurecr.io, because the ACR detection regex is unanchored. A Dockerfile that pulls from a lookalike host such as x.azurecr.io.attacker.com hands the build's Azure identity token to the attacker, who can use it against Azure with that identity's role assignments.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-02 17:24 UTC. All times on this page are UTC.
Teams that run kaniko to build container images on Azure or with Azure identities available to the build, and that have no Docker config credentials for the registries they pull from. Builds that only use Google or Amazon ECR, or that have credentials set for every registry in the Docker config, are not reached through this path. The exposure needs the build to reference an attacker-controlled host, so review Dockerfile inputs from untrusted sources.
No product ranges from the sources yet.
executor version or the image tag, and confirm it is below 1.25.20.FROM or COPY --from= references to hosts containing .azurecr.io, .azurecr.cn, or that are not your own registry..azurecr.de.azurecr.us1.25.20 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-105769")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.