Quick answers
- Is CVE-2026-54582 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-54582 being exploited in the wild.
- How severe is CVE-2026-54582?
- Informational severity, published 17 September 2026.
- Which products and versions are affected?
- MidnightBSD Mport prior to 2.7.8.
- Is there a fix for CVE-2026-54582?
- A patch was published on 2026-05-14: Fix merged in commit c643312d149dcc994957dbafa8f6f6b61e945e39 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-54582 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-54582?
- Check whether you run MidnightBSD Mport at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a missing input validation check in the package installation logic. Prior to version 2.7.8, the MPORT_PRECHECK_FILE_CONFLICTS precondition check was not applied across libmport/check_preconditions.c, libmport/install_primative.c, and libmport/mport_private.h, allowing incoming packages to overwrite existing files without detection. The check is bypassed only when the mport->force flag is explicitly enabled; normal privileged installation without this override is protected. An attacker with local access and ability to explicitly force package installation could craft a malicious or conflicting package to overwrite files owned by other packages or untracked by mport, compromising filesystem and package database integrity. This issue is fixed in version 2.7.8 by adding proper file conflict detection before installation.
Affected products
- MidnightBSD mport prior to 2.7.8
Timeline
- 2026-05-14: patched: Fix merged in commit c643312d149dcc994957dbafa8f6f6b61e945e39
- 2026-09-17: disclosed