mport is the MidnightBSD Package Manager. Prior to 2.7.8, mport_verify_package() in libmport/verify.c could continue after MD5File() or SHA256_File() failed and compare an expected checksum with stale data in the hash buffer rather than a newly computed digest. An attacker able to influence an installed file or the conditions that make hashing fail could receive a misleading integrity result or hide a checksum failure. This issue is fixed in version 2.7.8.
CVE-2026-54578
LOWPre-NVD 2.02.0Trending — 3 sources updated this week
EchelonGraph scoreLOW confidence
This low-severity CVE scores 2.0 under a secondary CVSS source (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: secondary
2.0EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 2.0Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 2.0
- EG Score
- 2.0(low)
- EG Risk
- 9(Track)EG Risk 9/100SSVC: Track
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 computedSeverity20% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 1%
- KEV
- Not listed
Published
September 17, 2026
Last Modified
September 18, 2026
References (4)
- security-advisories@githubhttps://github.com/MidnightBSD/mport/commit/cd9991c3cc1f60ecb3f378852ad8b5caa820e990
- security-advisories@githubhttps://github.com/MidnightBSD/mport/pull/138
- security-advisories@githubhttps://github.com/MidnightBSD/mport/releases/tag/2.7.8
- security-advisories@githubhttps://github.com/MidnightBSD/mport/security/advisories/GHSA-hgmr-9p75-q5cg
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 6× 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.
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 15:26 UTCEG score recompute
- 2026-09-18 14:54 UTCEG score recompute
- 2026-09-17 17:35 UTCEG score recompute
- 2026-09-17 17:00 UTCEG score recompute
- 2026-09-17 16:59 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-54578?
CVE-2026-54578 is a low vulnerability published on September 17, 2026. mport is the MidnightBSD Package Manager. Prior to 2.7.8, mportverifypackage() in libmport/verify.c could continue after MD5File() or SHA256_File() failed and compare an expected checksum with stale data in the hash buffer rather than a newly computed digest. An attacker able to influence an…
When was CVE-2026-54578 disclosed?
CVE-2026-54578 was first published in the National Vulnerability Database on September 17, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54578 actively exploited?
CVE-2026-54578 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.7% of all scored CVEs.
What is the CVSS score of CVE-2026-54578?
CVE-2026-54578 has a CVSS v3 base score of 2.0 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-54578?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54578, 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-54578
Is Your Infrastructure Affected by CVE-2026-54578?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.