EM-20261105-0LCS
VulnerabilityCritical severity
Critical kaniko Vulnerability (CVE-2026-105769)
CVE-2026-105769
Status
Developing
Since : signals keep joining.
- First Signal
- Nov 02 17:17 UTCC6 NVD CVE API 2.0
- Page Born
- Nov 05 17:48 UTCsecond source joined
- Last Signal
- Nov 05 17:48 UTC12 hours before snapshot
- Sources
- 20 official · 2 research, news or crowd
- Open For
- 3 daysso far
Life Of This Page
- 1BornA second, independent source names it.
- 2Developing · NowNew signals join; severity can move.
- 3ConfirmedNot yetCISA KEV lists it, or exploitation in the wild is reported.
- 4ResolvedNot yetPast the fix deadline and 14 days with no new signal.
- 5ArchivedNot yet30 days after resolved. Read only; the link keeps working. Reopens if it comes back.
The ID never changes, and earlier addresses keep working. A correction is logged, never overwritten. If two pages turn out to be one incident, the later one points to the earlier.
Vulnerability Lifecycle
- Disclosed: reachedNov 02 17:17 UTCC6 NVD published
- Scored: reachedNov 02 17:17 UTCCVSS 9.3 · EPSS 0.2%
- Exploited: not yetNot yetNo exploitation reported
- Advisories: not yetNot yetNone yet
- Vendor Response: not yetNot yetNone in sources yet
- Resolved: not yetNot yetAfter 14 quiet days
Timeline
Point at a mark to read it. Squares are signals, colored by severity; every one is also listed under Signals.
Signals
- GHSA-5q7h-w9jf-cx97 / CVE-2026-105769: kaniko can send the build's Azure (Entra ID) access token to lookalike ACR registry hosts (opens source in a new tab) go:github.com/chainguard-dev/kaniko Crit severityDatabaseC26 GitHub Advisory Database
- CVE-2026-105769 (CVSS 9.3) (opens source in a new tab) 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/chrism… Crit severityDatabaseC6 NVD CVE API 2.0