Quick answers
- Is CVE-2026-54585 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-54585 being exploited in the wild.
- How severe is CVE-2026-54585?
- 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-54585?
- A patch was published on 2026-05-14: Fixed in version 2.7.8 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-54585 attacked?
- It is attacked over the network or with local access, in a software library.
- Am I affected by CVE-2026-54585?
- 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
A path traversal vulnerability exists in the create_sample_file() function in libmport/bundle_read_install_pkg.c prior to version 2.7.8. The function fails to properly constrain absolute source and destination paths specified in the sample-file manifest directive to the configured mport installation root, allowing an attacker-controlled package manifest to direct file operations outside the intended root directory. An attacker can craft a malicious package containing sample-file directives with absolute paths that, when processed by privileged mport operations, write arbitrary files to the filesystem. The vulnerability requires a user to install or process a malicious package, but would be exploited with package manager privileges. The issue is fixed in version 2.7.8.
Affected products
- MidnightBSD mport prior to 2.7.8
Timeline
- 2026-09-17: disclosed
- 2026-05-14: patched: Fixed in version 2.7.8