Vulnerability in chainguard.dev/apko (CVE-2026-42576)
Summary
Vulnerability in chainguard.dev/apko (CVE-2026-42576). Risk of unauthorized operations or information disclosure. Exploitable via DiscoverKeys. Mitigation: upgrade to 1.2.7 or later.
Original description
The description as published by the source.
apko allows users to build and publish OCI container images built from apk packages. Prior to version 1.2.7, DiscoverKeys in pkg/apk/apk/implementation.go unconditionally type-asserts JWKS keys as *rsa.PublicKey without checking the key type. If a repository JWKS endpoint returns a non-RSA key (e.g. EC), the unchecked assertion panics and crashes apko. This affects any workflow that initializes the APK database and fetches repository keys. This issue has been patched in version 1.2.7.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-42576 has been found in chainguard.dev/apko.
Attackers can target a specific entry point like DiscoverKeys over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.5/10.
What to do: upgrade chainguard.dev/apko to 1.2.7 or later.
If unsure, ask your IT team or search "chainguard.dev/apko CVE-2026-42576" on the vendor's site.
CVE-2026-42576 (chainguard.dev/apko) — CWE-704 / CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: DiscoverKeys
Patched: 1.2.7 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-704) exists in chainguard.dev/apko. Attackers reach the vulnerable code path via DiscoverKeys without authentication.
Check the vendor advisory for the affected versions of chainguard.dev/apko. Attack surface: DiscoverKeys.
Severity: Medium (CVSS 6.5/10). Risk of unauthorized operations or information disclosure.
Update to 1.2.7.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'chainguard.dev/apko' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'chainguard.dev/apko' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
chainguard.dev/apkoを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade chainguard.dev/apko to 1.2.7ステージング環境で 1.2.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web github.com
- web github.com