CVE-2026-54578

mport verify can compare stale checksum data after hashing failures

LOW
2
CVSS Score
Published: September 17, 2026 at 04:54 PM UTC
Updated: September 18, 2026 at 03:17 PM UTC
1 product affected across 1 vendorMport

Using mport by MidnightBSD?

Get instant alerts when new vulnerabilities affect mport - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
LOW2
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 2.7.8
Affected range stops below 2.7.8, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

2LOWGitHub_M
Vector?

Quick Info

StatusDEFERRED
CWE
CWE-354CWE-755

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card