CVE-2026-54174

HIGHPre-NVD 8.38.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (4th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
8.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 8.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
8.3
EG Score
8.3HIGHmedium confidence
EG Risk
37
EG Risk 37/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity83% × 45%
The EG Score, 8.3 of 10.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
4th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 10, 2026

Last Modified

September 30, 2026

Advisory Details (1)

Auto-updated Sep 11, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

Incomplete package integrity verification allows data section substitution · Advisory · chainguard-dev/melange · GitHub

https://github.com/chainguard-dev/melange/security/advisories/GHSA-fpg8-7664-jc5q

Vendor Advisories for CVE-2026-54174(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(2 across 1 ecosystem)
Go(2)
PackageVulnerable rangeFix by version rangeDependents
chainguard.dev/apko—
  • every version up to 1.2.9: fixed in 1.2.9
—
chainguard.dev/melange—
  • every version up to 0.50.4: fixed in 0.50.4
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 32× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  2. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  3. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  4. 2026-10-12 15:56 UTCEG score recompute
  5. 2026-10-11 19:40 UTCEG score recompute
  6. 2026-10-11 16:55 UTCEG score recompute
  7. 2026-10-11 14:18 UTCEG score recompute
  8. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  11. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  12. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  13. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  14. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  15. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  16. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  17. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  18. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  19. 2026-09-30 20:04 UTCEG score recompute
  20. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  21. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  22. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  23. 2026-09-28 09:45 UTCEG score recompute
  24. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  25. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
Show 14 more
  1. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  2. 2026-09-23 05:43 UTCEG score recompute
  3. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  4. 2026-09-18 05:16 UTCEG score recompute
  5. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  6. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  7. 2026-09-14 18:08 UTCEG score recompute
  8. 2026-09-14 16:36 UTCEG score recompute
  9. 2026-09-13 08:10 UTCEG score recompute
  10. 2026-09-11 21:24 UTCEG score recompute
  11. 2026-07-30 11:11 UTCEG score recompute
  12. 2026-07-26 12:07 UTCEG score recompute
  13. 2026-07-23 03:19 UTCEG score recompute
  14. 2026-07-10 22:12 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-54174?
CVE-2026-54174 is a high-severity vulnerability; its CVE record was published on July 10, 2026. 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…
When was the CVE record for CVE-2026-54174 published?
The CVE record for CVE-2026-54174 was published on July 10, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-54174 actively exploited?
CVE-2026-54174 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54174?
CVE-2026-54174 has a CVSS base score of 8.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-54174?
A fix for CVE-2026-54174 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-54174 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54174

Explore →

Is Your Infrastructure Affected by CVE-2026-54174?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs