Vulnerability Description
apko allows users to build and publish OCI container images built from apk packages. Prior to version 1.2.7, apko verifies the signature on APKINDEX.tar.gz but never compares individually downloaded .apk packages against the checksum recorded in the signed index. The checksum is parsed and available via ChecksumString(), and the downloaded package control hash is computed, but the two values are never compared in getPackageImpl(). Mismatched packages are silently accepted. An attacker who can substitute download responses (compromised mirror, HTTP repository, poisoned CDN cache) can install arbitrary packages into built images. This issue has been patched in version 1.2.7.
CVSS Score
HIGH
Related Weaknesses (CWE)
References
- https://github.com/chainguard-dev/apko/commit/a118c3d604107532b5525bd4bee2fb369a
- https://github.com/chainguard-dev/apko/releases/tag/v1.2.7
- https://github.com/chainguard-dev/apko/security/advisories/GHSA-hcwr-pq9g-rq3m
FAQ
What is CVE-2026-42575?
CVE-2026-42575 is a vulnerability with a CVSS score of 7.5 (HIGH). apko allows users to build and publish OCI container images built from apk packages. Prior to version 1.2.7, apko verifies the signature on APKINDEX.tar.gz but never compares individually downloaded ....
How severe is CVE-2026-42575?
CVE-2026-42575 has been rated HIGH with a CVSS base score of 7.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-42575?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.