Skip to main content
VulnerabilityPublished

CVE-2026-54581: MidnightBSD mport · Insufficient Verification of Data Authenticity

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.2% chance of exploitation in 30 days – higher than 12% 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 MidnightBSD mport to version 2.7.8 or later, where this vulnerability is fixed. No other mitigation is indicated as the issue is resolved by this official fix.

Description

mport is the MidnightBSD Package Manager. Prior to 2.7.8, the mport_fetch_bootstrap_index() function in libmport/fetch.c could return success when bootstrap index hash verification encountered a missing or invalid hash because the failure path did not preserve a fatal result. A network attacker or compromised mirror able to alter bootstrap index content or its transport path could therefore cause mport to proceed with an unverified or tampered bootstrap package index. This issue is fixed in version 2.7.8.

References

Community reviews

Loading reviews…