cve.bz

CVE-2026-54174 chainguard-dev

8.3 highEPSS 0.2%Fix available

High (8.3) in chainguard-dev. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in chainguard.dev/apko 1.2.9.

On this page
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.

Severity

CVSS 3.1

8.3 high
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 5th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-09-14. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-345 Insufficient Verification of Data Authenticity
CWE-354 Improper Validation of Integrity Check Value
OWASP Top 10
A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-54174 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-54174?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-54174?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-54174 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
chainguard-dev melange< 0.50.4
chainguard-dev apko< 1.2.9

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-fpg8-7664-jc5qGochainguard.dev/apko<1.2.91.2.9
GHSA-fpg8-7664-jc5qGochainguard.dev/melange<0.50.40.50.4
GO-2026-5968Gochainguard.dev/apko<1.2.91.2.9
GO-2026-5968Gochainguard.dev/melange<0.50.40.50.4

Linux distributions

DistributionReleasePackageFixed inAdvisory
openSUSELeap 16.0govulncheck-vulndb0.0.20260723T184607-160000.1.1openSUSE-SU-2026:21483-1
openSUSETumbleweedapko1.4.4-1.1openSUSE-SU-2026:11829-1

From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: openSUSE.

Attack patterns (CAPEC)

  • CAPEC-75 Manipulating Writeable Configuration Files Likelihood: High · Severity: Very High
  • CAPEC-145 Checksum Spoofing Severity: Medium
  • CAPEC-463 Padding Oracle Crypto Attack Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-345 (12).

References

Check your stackJSON