Skip to main content
VulnerabilityPublished

CVE-2026-54583: MidnightBSD mport · Path Traversal

Affects MidnightBSD mportSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.3 High : upgrade to 2.7.8 soon.

Data as of 1 Nov 2026, 11:03 UTC

CVSS 4.0 base score
8.3High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.7.8
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 1 Nov 2026.

What to do

Upgrade mport and midnightbsd/mport to 2.7.8.

Affected software

ProductAffectedFixed in
MidnightBSDmportAffected
  • <2.7.8
Fixed in
  • 2.7.8
GitHubmidnightbsd/mportpkg:github/midnightbsd/mportOther threatsAffected
  • <2.7.8
Fixed in
  • 2.7.8

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade mport to version 2.7.8 or later, where the vulnerability is fixed by proper validation of bundle filenames. No other mitigation is required as the fix addresses the root cause.

Description

mport is the MidnightBSD Package Manager. Prior to 2.7.8, libmport/fetch.c did not consistently reject empty, dot, dot-dot, or slash-containing bundle filenames before composing package download and write paths. Malicious package index data could place an unsafe value in indexEntry->bundlefile, and the missing is_valid_bundle_filename() checks allowed downloaded package data to be written outside the intended cache location or to an unsafe destination name. This issue is fixed in version 2.7.8.

References

Community reviews

Loading reviews…