Skip to main content
VulnerabilityPublished Updated

CVE-2026-42575: chainguard-dev apko · Insufficient Verification of Data Authenticity

Affects chainguard-dev apkoSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 1.2.7 soon.

Data as of 10 Nov 2026, 23:24 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.2.7
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.

What to do

Upgrade apko and chainguard-dev/apko to 1.2.7.

Affected software

ProductAffectedFixed in
chainguard-devapkoAffected
  • <1.2.7
Fixed in
  • 1.2.7
GitHubchainguard-dev/apkopkg:github/chainguard-dev/apkoOther threatsAffected
  • <1.2.7
Fixed in
  • 1.2.7

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade apko to version 1.2.7 or later, where this vulnerability has been patched. Prior to upgrading, be cautious of using untrusted mirrors or HTTP repositories for package downloads. Patch status is not explicitly stated but the description confirms the issue is fixed in version 1.2.7.

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.

References

Community reviews

Loading reviews…