Content Quality: Clear News write-up (856 words, within the 400-1200 range) of a GitHub Advisory Database entry: lead states the advisory's own wording, then mechanism, fix and workarounds, a dated timeline of the underlying helper flaw, and a What Is Not Known section. Title is 134 characters (under the 150-character guideline). Not human-requested.
Source Verification: All six snapshots read in full from sources/2026-11/ (gunzipped, HTML stripped to text; sha256 of each uncompressed snapshot re-computed and matches the manifest; no suspicious_patterns on any source; no embedded instructions found). source-0 (github.com/advisories/GHSA-5q7h-w9jf-cx97, chainguard-forks/kaniko, package github.com/chainguard-dev/kaniko): CONFIRMED the quoted sentence 'can send a Microsoft Entra ID (Azure AD) access token for Azure Resource Manager to a registry host an attacker controls' verbatim; affected '< 1.25.20', patched '1.25.20'; Critical, CVSS 9.3, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N (the page lists the score and vector but does not say who scored it; the article only says the advisory 'lists' it, which is accurate; the reporter independently proposed the identical vector and 9.3 in sources 3 and 5); FROM x.azurecr.io.attacker.com/img example; no RUN needed and no push needed; unanchored regex matching .azurecr.io/.cn/.de/.us; the three identity kinds (service principal env vars, federated workload identity token as injected by AKS workload identity, managed identity via IMDS or MSI_ENDPOINT); built-in helper consulted for registries without Docker-config credentials that are not Google or Amazon ECR, covering FROM and COPY --from; impact (ARM token, /oauth2/exchange of a real ACR, AcrPush push); patched helper accepts exactly host[:port] with mcr.microsoft.com or a well-formed .azurecr.* name; kaniko no longer depends on the upstream module; repository publishes no binaries or images, rebuild executor, warmer and helper binary; workarounds (remove Azure credentials, federated tokens, MSI_ENDPOINT/MSI_SECRET and block 169.254.169.254; AZURE_ENVIRONMENT=none for those not relying on built-in ACR auth; treat tokens as compromised, leaked token valid until expiry, rotation does not revoke); credit 'Reported by Martin Zihlmann (@mzihlmann) of osscontainertools'. The advisory's further workaround for credsStore 'acr-env' and its log-review advice are not mentioned in the article; omission, not misstatement. Advisory shows EPSS 0.196% and no report of exploitation. source-1 (chainguard-forks/kaniko release v1.25.20): CONFIRMED released by 8none1 on 27 Oct (datetime 2026-10-27T19:05:06Z), entry 'Fix GO-2026-6225: carry a patched docker-credential-acr-env inside the kaniko module by @8none1 in #495'. source-2 (pkg.go.dev/vuln/GO-2026-6225): CONFIRMED Published Aug 18, 2026 (Modified Aug 25), affects github.com/chrismellard/docker-credential-acr-env/pkg/credhelper, 'all versions, no known fixed', credit Martin Zihlmann, unanchored-regex description. source-3 (chrismellard/docker-credential-acr-env#21): CONFIRMED opened by mzihlmann on Aug 13, 2026; acrRE unanchored; 'Everything up to and including 0.7.0 is affected'; 'We started a new fork under https://github.com/osscontainertools/docker-credential-acr and released the fix under v0.8.0'; Activity section has no comments, so 'shows no comments' holds. source-4 (kyverno/kyverno#17266): CONFIRMED opened Aug 20, 2026 by Sashang-debug, Kyverno 1.18.0 (main branch), govulncheck flagged GO-2026-6225, asks that the dependency be 'replaced or patched', issue Open. source-5 (golang/vulndb#6331): CONFIRMED opened by mzihlmann on Sep 1, 2026; stevebeattie commented on Nov 2, 2026: 'On 2026-11-02 we published GHSA-5q7h-w9jf-cx97 and CVE-2026-105769 through the Chainguard CNA' (article's quoted fragment 'we published GHSA-5q7h-w9jf-cx97' is verbatim); both cover github.com/chainguard-dev/kaniko before v1.25.20 only; 'CVE-2026-105769 doesn't cover github.com/chrismellard/docker-credential-acr-env itself' (article paraphrases without quote marks, accurately); 'The upstream module still has no CVE'; reporter wrote that consumers inherit the module via go-containerregistry/pkg/authn/k8schain and krane. Exploitation: none of the six sources reports exploitation (checked each), so the article's statement holds. Independence: the Go vulnerability database entry (source 2) and the Kyverno issue (source 4) are third-party records, though the Go entry credits the same reporter and was built from his disclosure; the GHSA (0) and release page (1) are Chainguard-fork vendor material; the helper issue (3) and the vulndb issue (5) are written by the reporter, the latter with a Chainguard commenter. Independent-of-subject count: 2 (one of them derived from the reporter's report). No news outlet is cited, and the article says so. This is a News piece, so the Analysis requirements do not apply. Allowlist: github.com (line 1139) and pkg.go.dev (line 2256) are both on config/source_allowlist.txt; no additions needed.
Factual Accuracy: Every version, date, identifier and name checked against raw snapshot text: kaniko before v1.25.20 / fixed in 1.25.20; GHSA-5q7h-w9jf-cx97; CVE-2026-105769; GO-2026-6225; CVSS 9.3 and vector; 2026-08-13 helper issue; 2026-08-18 Go database publication; 2026-08-20 Kyverno issue; 2026-10-27 release; 2026-11-02 Chainguard statement; v0.8.0 and 0.7.0; PR 495; the named people (Martin Zihlmann, mzihlmann, 8none1, stevebeattie). No fabricated specific found. 'Go database lists no known fixed version' and 'does not cover the upstream helper module' match the sources' wording. Chainguard is described neutrally as the publisher of the advisory and CVE; the article does not blame any party. 'The helper flaw was public months before the kaniko advisory' is accurate (Aug 13/18 against Nov 2). Minor imprecision, not a correction: 'users must rebuild' restates the advisory's imperative 'Rebuild the executor...'.
Overall Assessment: Accurate, carefully hedged, fully sourced vulnerability coverage; every quote, date, version and identifier traces to a cited snapshot, and the article correctly limits CVE-2026-105769 to the Chainguard kaniko fork and reports no exploitation. APPROVE. Featured candidacy: 1 - solid, accurate security advisory coverage for developers running kaniko builds with Azure identities, not a broad-audience story