# CVE-2026-105769: kaniko can send the build's Azure (Entra ID) access token to lookalike ACR registry hosts

Status: published. Published: 2026-11-02. Updated: 2026-11-02.

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.

## Remediation

- 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: chainguard)
- workaround: 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: chainguard)
- fix: The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches. (source: CNA: chainguard) — https://github.com/chainguard-forks/kaniko/pull/495
- fix: 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-cx97) — https://github.com/chainguard-forks/kaniko/security/advisories/GHSA-5q7h-w9jf-cx97

## Affected products and versions

- chainguard / kaniko (github.com/chainguard-dev/kaniko): ≥ 0; < 1.25.20 (affected, semver). Source: CNA: chainguard
-  / github.com/chainguard-dev/kaniko (github.com/chainguard-dev/kaniko): < 1.25.20 (affected, GitHub advisory range). Source: GitHub GHSA-5q7h-w9jf-cx97

## Severity and prioritization

- CVSS 3.1: 9.3 (critical); CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N; source: CNA: chainguard

- CVSS 3.1: 9.3 (critical); CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N; source: NVD: 82cea9a6-e9e3-46fe-bdb0-3673de380178

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: exploitation none; automatable no; technical impact total; source ADP: CISA-ADP

- Weaknesses: CWE-346, CWE-522

## 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-cx97 (CNA: chainguard; vendor-advisory)

- https://github.com/chainguard-forks/kaniko/pull/495 (CNA: chainguard; patch)

- https://github.com/chainguard-forks/kaniko/releases/tag/v1.25.20 (CNA: chainguard; release-notes)

- https://github.com/chrismellard/docker-credential-acr-env/issues/21 (CNA: chainguard; issue-tracking)

- https://pkg.go.dev/vuln/GO-2026-6225 (CNA: chainguard; third-party-advisory)

- https://github.com/chainguard-forks/kaniko/pull/495 (82cea9a6-e9e3-46fe-bdb0-3673de380178)

- https://github.com/chainguard-forks/kaniko/releases/tag/v1.25.20 (82cea9a6-e9e3-46fe-bdb0-3673de380178)

- https://github.com/chainguard-forks/kaniko/security/advisories/GHSA-5q7h-w9jf-cx97 (82cea9a6-e9e3-46fe-bdb0-3673de380178)

- https://github.com/chrismellard/docker-credential-acr-env/issues/21 (82cea9a6-e9e3-46fe-bdb0-3673de380178)

- https://pkg.go.dev/vuln/GO-2026-6225 (82cea9a6-e9e3-46fe-bdb0-3673de380178)

- https://github.com/chainguard-forks/kaniko/security/advisories/GHSA-5q7h-w9jf-cx97 (GitHub Security Advisories; advisory)

## Provenance

- CNA: chainguard: https://www.cve.org/CVERecord?id=CVE-2026-105769; retrieved 2026-11-02; source updated 2026-11-02

- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-105769; retrieved 2026-11-02; source updated 2026-11-02

- GitHub Security Advisories: https://github.com/chainguard-forks/kaniko/security/advisories/GHSA-5q7h-w9jf-cx97; retrieved 2026-11-02; source updated 2026-11-02

Revision: bc884e3aa4d7d40e454a3aef764f9fea94d5eb71df2f36472d817be5f6daa703

Canonical: https://y2.dev/cve/CVE-2026-105769

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.