Is CVE-2026-105769 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-105769 being exploited in the wild.

How severe is CVE-2026-105769?

Critical severity, with a CVSS score of 9.3, published 2 November 2026.

Which products and versions are affected?

github.com/chainguard-dev/kaniko (Go) < 1.25.20, SEMVER:introduced=0,fixed=1.25.20; Google Kaniko before 1.25.20.

How is CVE-2026-105769 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-105769?

Check whether you run github.com/chainguard-dev/kaniko (Go) or Google Kaniko at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-105769: kaniko Azure credential theft via unanchored regex in ACR helper

Q: Is there a fix for CVE-2026-105769?

Yes. github.com/chainguard-dev/kaniko (Go): upgrade to 1.25.20 or later. Until then: Do not use kaniko to build untrusted Dockerfiles, or restrict its execution environment to have minimal Azure IAM permissions. Disable or restrict the Azure credential helper if not required for your use case. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-105769 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-105769?

Check whether you run github.com/chainguard-dev/kaniko (Go) or Google Kaniko at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-105769 · Severity: critical · CVSS 9.3 · Published 2026-11-02

kaniko is a container image builder that can automatically authenticate to image registries using cloud provider credentials. Before version 1.25.20, kaniko used a flawed credential helper that could be tricked into sending Azure authentication tokens to attacker-controlled registries by using lookalike domain names. An attacker can exploit this by crafting a malicious container image reference in a Dockerfile, causing kaniko to leak Azure credentials that could be used to access or modify cloud resources.

Vendors: Go, Google.

Quick answers

Is CVE-2026-105769 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-105769 being exploited in the wild.
How severe is CVE-2026-105769?: Critical severity, with a CVSS score of 9.3, published 2 November 2026.
Which products and versions are affected?: github.com/chainguard-dev/kaniko (Go) < 1.25.20, SEMVER:introduced=0,fixed=1.25.20; Google Kaniko before 1.25.20.
Is there a fix for CVE-2026-105769?: Yes. github.com/chainguard-dev/kaniko (Go): upgrade to 1.25.20 or later. Until then: Do not use kaniko to build untrusted Dockerfiles, or restrict its execution environment to have minimal Azure IAM permissions. Disable or restrict the Azure credential helper if not required for your use case. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-105769 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-105769?: Check whether you run github.com/chainguard-dev/kaniko (Go) or Google Kaniko at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/chainguard-dev/kaniko (Go): upgrade to 1.25.20 or later
```
go get github.com/chainguard-dev/kaniko@v1.25.20
```

Do not use kaniko to build untrusted Dockerfiles, or restrict its execution environment to have minimal Azure IAM permissions. Disable or restrict the Azure credential helper if not required for your use case.

Technical details

The vulnerability exists in the Azure Container Registry (ACR) credential helper used by kaniko, which employs an unanchored regular expression to identify ACR registry hosts. This allows any hostname containing strings like .azurecr.io to be accepted, including domains such as x.azurecr.io.attacker.com. When kaniko encounters a Dockerfile reference to such a lookalike host with no pre-configured credentials, it consults the helper, which obtains an Azure AD access token from the build environment (service principal, managed identity, or federated workload identity) and sends it to the attacker-controlled domain via an /oauth2/exchange endpoint. The attacker can then use this token to access Azure Resource Manager or any ACR registry the compromised identity can access.

Affected products

Google kaniko before 1.25.20

Identifiers

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

Timeline

2026-11-02: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.