Quick answers
- Is CVE-2026-54583 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-54583 being exploited in the wild.
- How severe is CVE-2026-54583?
- Informational severity, published 17 September 2026.
- Which products and versions are affected?
- MidnightBSD Mport before 2.7.8.
- Is there a fix for CVE-2026-54583?
- A patch was published on 2026-05-15: Fix merged in pull request #125 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-54583 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-54583?
- 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 path traversal flaw in libmport/fetch.c where the is_valid_bundle_filename() validation was not consistently applied before using package bundle filenames from index data. An attacker controlling or poisoning a package index could inject malicious values (empty strings, dot, dot-dot, or paths containing slashes) into the bundlefile field, causing mport to write downloaded packages to arbitrary filesystem locations. This requires the package index to be compromised or the user to be directed to a malicious index. The fix, deployed in version 2.7.8, adds proper filename validation before download and file write operations.
Affected products
- MidnightBSD mport before 2.7.8
Timeline
- 2026-09-17: disclosed
- 2026-05-15: patched: Fix merged in pull request #125