# CVE-2026-54585: mport sample file handling can write outside the configured root

> A malicious package manifest can write files outside the installation root, compromising local filesystem integrity in MidnightBSD's mport.

- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-xqjc-rxmm-p27v

## What is CVE-2026-54585?

CVE-2026-54585 is a medium-severity path traversal vulnerability in MidnightBSD mport, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

mport is the MidnightBSD Package Manager. Prior to 2.7.8, create_sample_file() in libmport/bundle_read_install_pkg.c did not constrain absolute source and destination paths from the sample-file manifest directive to mport->root. A malicious or malformed package manifest could therefore direct privileged sample-file handling to copy or write outside the configured installation root, compromising local filesystem integrity. This issue is fixed in version 2.7.8.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-54585?


## How do I fix CVE-2026-54585?

No fix has been published for CVE-2026-54585 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-54585 being exploited?

There is no known exploitation of CVE-2026-54585 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54585 and fix it if it is affected.

What it is: CVE-2026-54585 is a medium-severity path traversal vulnerability in MidnightBSD mport, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-54585 in the wild and no public exploit code.

Affected product: MidnightBSD mport. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54585/ (Markdown: https://insights.sbomify.com/CVE-2026-54585/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54585
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54585
- OSV: https://osv.dev/vulnerability/CVE-2026-54585

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54585/
Summaries are generated and may contain mistakes; the official description above is the record.