Approved changes feed: RSS · Atom
cpe:2.3:a:chainguard-dev:apko:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Chainguard Dev (e4a5b167-64af-5fee-bf1f-c2ee974e318c) |
|---|---|
| Product | Apko (1bf1be62-3bb2-5438-be2b-74489e5ebbd2) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-54174 |
vulnerable | 2026-09-16 04:33:28.500525 |
melange: Incomplete package integrity verification allows data section substitution
HIGH (8.3)
melange allows users to build apk packages using declarative pipelines. Apko prior to version 1.2.9, corresponding to melange prior to version 0.50.4, 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. Apko version 1.2.9 and melange version 0.50.4 contain a fix.
Published: 2026-09-11T21:05:30.789Z
Updated: 2026-09-14T16:19:01.111Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-42576 |
vulnerable | 2026-06-08 08:03:16.525495 |
apko `DiscoverKeys` has a panic on non-rsa jwks key that causes crash during key discovery
MEDIUM (6.5)
apko allows users to build and publish OCI container images built from apk packages. Prior to version 1.2.7, DiscoverKeys in pkg/apk/apk/implementation.go unconditionally type-asserts JWKS keys as *rsa.PublicKey without checking the key type. If a repository JWKS endpoint returns a non-RSA key (e.g. EC), the unchecked assertion panics and crashes apko. This affects any workflow that initializes the APK database and fetches repository keys. This issue has been patched in version 1.2.7.
Published: 2026-05-09T19:26:56.224Z
Updated: 2026-05-11T14:57:58.452Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-42575 |
vulnerable | 2026-06-08 08:03:16.525238 |
apko doesn't verify downloaded apk packages against APKINDEX checksum (package substitution possible)
HIGH (7.5)
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.
Published: 2026-05-09T19:26:27.415Z
Updated: 2026-05-13T17:45:37.672Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-42574 |
vulnerable | 2026-06-08 08:03:16.524833 |
apko dirFS has a symlink-following path traversal that allows multiple entry points to escape the build root
HIGH (7.5)
apko allows users to build and publish OCI container images built from apk packages. From version 0.14.8 to before version 1.2.5, a crafted .apk could install a TypeSymlink tar entry whose target pointed outside the build root, and a subsequent directory-creation or file-write entry in the same or later archive could traverse that symlink to reach host paths the build user could write to. This issue has been patched in version 1.2.5.
Published: 2026-05-09T19:24:48.497Z
Updated: 2026-05-11T17:11:40.244Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-25140 |
vulnerable | 2026-06-08 07:53:19.042084 |
apko affected by potential unbounded resource consumption in expandapk.ExpandApk on attacker-controlled .apk streams
HIGH (7.5)
apko allows users to build and publish OCI container images built from apk packages. From version 0.14.8 to before 1.1.1, an attacker who controls or compromises an APK repository used by apko could cause resource exhaustion on the build host. The ExpandApk function in pkg/apk/expandapk/expandapk.go expands .apk streams without enforcing decompression limits, allowing a malicious repository to serve a small, highly-compressed .apk that inflates into a large tar stream, consuming excessive disk space and CPU time, causing build failures or denial of service. This issue has been patched in version 1.1.1.
Published: 2026-02-04T19:02:20.988Z
Updated: 2026-02-04T19:17:36.596Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-25122 |
vulnerable | 2026-06-08 07:53:19.019518 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-25121 |
vulnerable | 2026-06-08 07:53:19.018253 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-53945 |
vulnerable | 2026-06-08 07:31:15.975949 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-36127 |
vulnerable | 2026-06-08 06:39:43.699261 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.