CVE-2026-42575

apko doesn't verify downloaded apk packages against APKINDEX checksum (package substitution possible)

State
Published
Severity
7.5 High
Published
May 9, 2026
Updated
May 13, 2026
Reserved
Apr 28, 2026

Read the record on cve.org

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.

Scores

CVSSScoreVectorSource
3.17.5 HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:NGitHub_M

Weaknesses

  • CWE-345 Insufficient Verification of Data Authenticity
  • CWE-494 Download of Code Without Integrity Check

Affected Products

ProductVersions
apkochainguard-dev
  • < 1.2.7Affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.