Chainguard kaniko Flaw CVE-2026-105769: Update Now
Published November 5, 2026 · Last updated November 5, 2026
The short version: CVE-2026-105769 is a critical-severity security flaw in Chainguard kaniko. The National Vulnerability Database (NVD) published it on November 2, 2026, and the score it lists is 9.3 out of 10. When FraudMeNot checked on November 5, 2026, CISA had not added CVE-2026-105769 to its Known Exploited Vulnerabilities catalog, so there was no public U.S. government confirmation of attacks yet. A fix is available, which is why this page focuses on who should update and how.
What the official record says about CVE-2026-105769
The record was filed by 82cea9a6-e9e3-46fe-bdb0-3673de380178. In its own words: "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."
Why kaniko admins should care
Severity scores use the Common Vulnerability Scoring System (CVSS). 82cea9a6-e9e3-46fe-bdb0-3673de380178 rated CVE-2026-105769 9.3 (Critical) under CVSS 3.1. Reading that rating in everyday terms: it can be reached over a network, including the internet; an attacker does not need an account; a user has to take an action, such as opening a file or link. If it is abused, the rated damage to keeping data private is high, to keeping data unaltered is high, and to keeping kaniko running is none. Scoring string: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N.
Affected kaniko releases
According to the record, these releases are vulnerable:
- versions before 1.25.20
The type of bug behind CVE-2026-105769
NVD classifies it using MITRE's Common Weakness Enumeration:
- CWE-346, Origin Validation Error. MITRE describes this class of bug as follows: "The product does not properly verify that the source of data or communication is valid."
- CWE-522, Insufficiently Protected Credentials. MITRE describes this class of bug as follows: "The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval."
Vendor remediation for CVE-2026-105769
The vendor advisory remediation for operators of kaniko, quoted for this page, is: "Upgrade kaniko to v1.25.20 or later (Chainguard GHSA-5q7h-w9jf-cx97 / release v1.25.20). If you vendor the ACR credential helper, use the patched helper shipped in v1.25.20+."
What to do about it
- Update now: Upgrade kaniko to v1.25.20 or later (Chainguard GHSA-5q7h-w9jf-cx97 / release v1.25.20). If you vendor the ACR credential helper, use the patched helper shipped in v1.25.20+.
- Who should act: IT teams, managed service providers, and developers who run or ship kaniko. Check every place it runs, including servers, build systems, containers, and older machines nobody watches closely.
- Read the official advisory from Chainguard (linked under Sources) for exact fixed builds and any temporary workaround if you cannot patch today.
- After patching, confirm the new version is actually running and review logs from November 2, 2026 onward for anything unusual.
- Home users: you do not need to buy or download anything because of CVE-2026-105769. A caller, text, or pop-up claiming your computer is "infected" with this CVE and asking for money or remote access is a scam.
CVE-2026-105769 record details from CISA and NVD
- Attack complexity for CVE-2026-105769: low
- CVE-2026-105769 CVSS scope: changed
- NVD sub-scores for CVE-2026-105769: exploitability 2.8, impact 5.8.
- Who mapped the weakness type: 82cea9a6-e9e3-46fe-bdb0-3673de380178 (Secondary)
- References in the NVD record: 5.
- CISA SSVC decision points for CVE-2026-105769 (from NVD): exploitation=none; automatable=no; technicalImpact=total (role: CISA Coordinator, SSVC 2.0.3).
Dates to know
- November 2, 2026: NVD publishes CVE-2026-105769.
- November 5, 2026: FraudMeNot checks the CISA KEV catalog; CVE-2026-105769 is not listed.
- November 2, 2026: most recent NVD update (record status: Awaiting Analysis).
Official references
Links listed in the NVD record (labels in brackets come from NVD):
- github.com/chainguard-forks/kaniko/pull/495
- github.com/chainguard-forks/kaniko/releases/tag/v1.25.20
- github.com/chainguard-forks/kaniko/security/advisories/GHSA-5q7h-w9jf-cx97
- github.com/chrismellard/docker-credential-acr-env/issues/21
- pkg.go.dev/vuln/GO-2026-6225
Sources
- NVD: CVE-2026-105769
- CVE.org: CVE-2026-105769
- Chainguard advisory
- Chainguard advisory
- Chainguard advisory
- MITRE CWE-346
- MITRE CWE-522
General education only, not security advice. Facts checked against the sources above on the date shown.