CVE-2026-54578

mport verify can compare stale checksum data after hashing failures

Published Sep 17, 2026 CVSS 4.0 · 2 Low EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The mport package manager’s verification routine, mport_verify_package(), can erroneously continue after a hash calculation fails and compare a supplied checksum with a residual object in the hash buffer. This flaw can lead to a misleading integrity result or allow a checksum failure to go undetected. The weakness is an improper handling of error states in cryptographic functions, reflected by CWE-354 (Incorrect Resource Management) and CWE-755 (Unexpected Error State).

Affected Systems

Any MidnightBSD system running the mport package manager before release 2.7.8 is affected. The vulnerability is present in all earlier versions and resolved in 2.7.8; no specific sub‑version ranges are listed outside this general cutoff.

Risk and Exploitability

The CVSS score of 2 indicates low severity, while the EPSS score of less than 1% suggests a very low probability of exploitation. The issue is not listed in the CISA KEV catalog. The most likely attack vector requires the attacker to influence a file on the system or create conditions that trigger a hashing failure, implying the attacker has either local or privileged access. Successful exploitation could allow an attacker to hide a failed checksum or trick the system into accepting a tampered package without detection.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade mport to version 2.7.8 or later
  • Verify that the installed mport package matches the expected hash after installation
  • Restrict file editing and prevent intentional or accidental hash function failures

Generated by OpenCVE AI on September 18, 2026 at 23:48 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Midnightbsd
Midnightbsd mport
Vendors & Products Midnightbsd
Midnightbsd mport
Type Values Removed Values Added
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.
Title mport verify can compare stale checksum data after hashing failures
Weaknesses CWE-354
CWE-755
References
Metrics cvssV4_0

{'score': 2, 'vector': 'CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-354

    Improper Validation of Integrity Check Value

  • CWE-755

    Improper Handling of Exceptional Conditions

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Sep 18, 2026, 2:44 PM
Reserved
Jun 15, 2026, 7:15 PM
Status
Deferred
Published
Sep 17, 2026, 5:16 PM
Modified
Sep 18, 2026, 3:17 PM