Kaniko's Azure token leak starts with a hostname check
A container build can carry more authority than the application it produces. Kaniko builds run with registry credentials and, on Azure, may also receive an Entra ID identity through a service principal, federated workload identity, or the Azure Instance Metadata Service. CVE-2026-105769 matters because one hostname check can move that Azure Resource Manager token to a host selected by whoever controls the image reference.
The GitHub-reviewed advisory describes the flaw as an origin validation error. It affects kaniko before v1.25.20 and assigns a CVSS v3.1 score of 9.3. The important detail is not the score alone. It is the order of operations: kaniko can ask the Azure credential helper for a token before it has established that the destination is a legitimate Azure Container Registry endpoint.
The trust decision before registry authentication
Kaniko uses docker-credential-acr-env to obtain credentials for Azure Container Registry.…