Previously, Apko verified the control section hash (`.PKGINFO` etc.) against the signed `APKINDEX`, but never verified the data section hash (the actual package files that get installed). An attacker who could compromise a mirror, poison a cache, or MITM a package fetch could substitute arbitrary file contents while the control hash check still passed.
Update chainguard.dev/apko to 1.2.9; chainguard.dev/melange to 0.50.4 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanmelange: Incomplete package integrity verification allows data section substitution affects chainguard.dev/apko (go), chainguard.dev/melange (go). Severity is high. Previously, Apko verified the control section hash (`.PKGINFO` etc.) against the signed `APKINDEX`, but never verified the data section hash (the actual package files that get installed). An attacker who could compromise a mirror, poison a cache, or MITM a package fetch could substitute arbitrary file contents while the control hash check still passed.
AI coding agents often install or upgrade packages automatically in go. A high vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|---|---|
| chainguard.dev/apkogo | <1.2.9 | 1.2.9 |
Previously, Apko verified the control section hash (`.PKGINFO` etc.) against the signed `APKINDEX`, but never verified the data section hash (the actual package files that get installed). An attacker who could compromise a mirror, poison a cache, or MITM a package fetch could substitute arbitrary file contents while the control hash check still passed.
Update chainguard.dev/apko to 1.2.9; chainguard.dev/melange to 0.50.4 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanmelange: Incomplete package integrity verification allows data section substitution affects chainguard.dev/apko (go), chainguard.dev/melange (go). Severity is high. Previously, Apko verified the control section hash (`.PKGINFO` etc.) against the signed `APKINDEX`, but never verified the data section hash (the actual package files that get installed). An attacker who could compromise a mirror, poison a cache, or MITM a package fetch could substitute arbitrary file contents while the control hash check still passed.
AI coding agents often install or upgrade packages automatically in go. A high vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|---|---|
| chainguard.dev/apkogo | <1.2.9 | 1.2.9 |
| chainguard.dev/melangego | <0.50.4 | 0.50.4 |
|---|
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard| chainguard.dev/melangego | <0.50.4 | 0.50.4 |
|---|
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard