CVE-2026-54174

HIGHPre-NVD 8.38.3
EchelonGraph scoreLOW confidence

This high-severity CVE scores 8.3 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:github_m
8.3
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: —CVSS: 8.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

melange: Incomplete package integrity verification allows data section substitution

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.

CVSS v3
8.3
EG Score
8.3(low)
EPSS
—
KEV
Not listed

Published

July 10, 2026

Last Modified

July 10, 2026

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.

Data Freshness Timeline

(refreshed 11× in last 7d / 11× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-07-15 19:13 UTCEG score recompute
  2. 2026-07-15 07:31 UTCEG score recompute
  3. 2026-07-14 19:50 UTCEG score recompute
  4. 2026-07-14 08:06 UTCEG score recompute
  5. 2026-07-13 20:24 UTCEG score recompute
  6. 2026-07-13 08:42 UTCEG score recompute
  7. 2026-07-12 21:00 UTCEG score recompute
  8. 2026-07-12 09:17 UTCEG score recompute
  9. 2026-07-11 21:36 UTCEG score recompute
  10. 2026-07-11 09:54 UTCEG score recompute
  11. 2026-07-10 22:12 UTCEG score recompute

Frequently asked(4)

What is CVE-2026-54174?
CVE-2026-54174 is a high vulnerability published on July 10, 2026. melange: Incomplete package integrity verification allows data section substitution 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…
When was CVE-2026-54174 disclosed?
CVE-2026-54174 was first published in the National Vulnerability Database on July 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-54174?
CVE-2026-54174 has a CVSS v4.0 base score of 8.3 (CNA self-assessment; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-54174?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54174, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for 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.

Start Free Scan →Browse All CVEs