Exposes Azure AD access tokens from kaniko builds, allowing ARM and ACR access via CI/CD pipelines used broadly across organizations; high potential for widespread cloud compromise.
CVE-2026-105769
kaniko leak of Azure AD tokens to attacker-controlled registries via credential helper
Is CVE-2026-105769 being exploited?
Not confirmed. CVE-2026-105769 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.20% probability of exploitation in the next 30 days.
How severe is CVE-2026-105769?
CVE-2026-105769 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-105769?
Yes. A fix has been recorded for CVE-2026-105769. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-105769 affect?
CVE-2026-105769 affects kaniko < 1.25.20, docker-credential-acr-env helper, CI/CD pipelines using kaniko, Azure Container Registry lookalike hosts. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-105769?
Upgrade to kaniko v1.25.20+, rotate Azure credentials, audit build registries
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Build-time token exfil lets attacker call Azure Resource Manager and exchange tokens for ACR credentials using the build identity until token expiry.
Immediate action required
- affected< 1.25.20
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
cisa ssvc
- exploitation
- none
- automatable
- no
- technical impact
- total
Assessed by CISA 2 Nov 2026 (SSVC 2.0.3).
timeline
- 2 Nov 2026Published
- 2 Nov 2026CISA SSVC assessment: exploitation none · same day later
- 2 Nov 2026CVE record last updated · same day later
- 3 Nov 2026Analysed by vulneraibility.com · 1 day later
also known as
- Advisorygithub.com /chainguard-forks/kaniko/security/advisories/GHSA-5q7h-w9jf-cx97
- Advisorypkg.go.dev /vuln/GO-2026-6225
- Patchgithub.com /chainguard-forks/kaniko/pull/495
- Linkgithub.com /chainguard-forks/kaniko/releases/tag/v1.25.20
- Linkgithub.com /chrismellard/docker-credential-acr-env/issues/21
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- OSV: advisory aliases and downstream package versions
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.