Skip to main content
VulnerabilityPublished Updated

CVE-2026-54577: MidnightBSD mport · Improper Input Validation

Affects MidnightBSD mportSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 2.0 Low : upgrade to 2.7.8 when convenient.

Data as of 1 Nov 2026, 11:03 UTC

CVSS 4.0 base score
2.0Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.7.8
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/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 issue is fixed by proper resetting of parsing state before argument processing. No other mitigation is required as the fix addresses the root cause.

Description

mport is the MidnightBSD Package Manager. Prior to 2.7.8, the audit command in mport/mport.c computed option-adjusted local_argv and local_argc values but passed the original argument entry to audit_package(). When an operator or automation used an option such as -r before a package name, stale optind state and the unadjusted argument could cause mport to audit the option token instead of the requested package, producing a false-negative or useless result that could leave a vulnerable package unidentified. The corrected parsing resets optind and optreset before using the adjusted local arguments. This issue is fixed in version 2.7.8.

References

Community reviews

Loading reviews…