Arbitrary package injection via unchecked APKINDEX checksum
Published May 9, 2026 · Updated May 9, 2026
Integrity verification failure in Chainguard apko before 1.2.7 allows remote attackers to place arbitrary packages in built images. The getPackageImpl() path computes the downloaded package control hash but never compares it with ChecksumString() from the signed APKINDEX. Exploitation requires control of download responses through a compromised mirror, an HTTP repository, or a poisoned CDN cache, and results in attacker-chosen content in produced OCI images.
Summary
What happened
Integrity verification failure in Chainguard apko before 1.2.7 allows remote attackers to place arbitrary packages in built images. The getPackageImpl() path computes the downloaded package control hash but never compares it with ChecksumString() from the signed APKINDEX. Exploitation requires control of download responses through a compromised mirror, an HTTP repository, or a poisoned CDN cache, and results in attacker-chosen content in produced OCI images.
The record
- CVE
- CVE-2026-42575
- Published
- May 9, 2026
- Updated
- May 9, 2026
- Vendor
- Chainguard
- Product
- apko
- Classifications
- CWE-345, CWE-494, T1195.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 9, 2026CVE publishedPublication date reported by the CVE source.
- May 9, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.2.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo