CVE-2026-54577: mport audit can inspect the wrong package when options are present

Published Sep 17, 2026
·
Updated

mport is the MidnightBSD Package Manager. Prior to 2.7.8, the audit command in mport/mport.c computed option-adjusted localargv and localargc values but passed the original argument entry to auditpackage(). 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.

Affected Software

1 affected component
mport<2.7.8

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade mport/mport to a version that resolves this vulnerability.

    Fixed in 2.7.8

Event History

Sep 17, 2026
CVE Published
via MITRE·04:49 PM
Data Sourced
via MITRE·04:49 PM
DescriptionWeakness

Frequently Asked Questions

1

Who is affected by this issue?

Operators and automation using mport versions before 2.7.8 may be affected when invoking the audit command with an option, such as -r, before a package name. The impact is an incorrect audit target and a potentially false-negative or otherwise useless audit result.

2

What conditions are needed to trigger the incorrect audit behavior?

The audit command must be run with options preceding the intended package name. Under that invocation pattern, stale option-parsing state and use of the unadjusted argument can cause the option token to be audited instead of the requested package.

3

How can I mitigate the issue if I cannot immediately upgrade?

Avoid placing audit-command options before the package name, since this is the invocation pattern described as causing the wrong package to be inspected. Treat prior audit results produced with options before a package name as potentially unreliable and rerun them without that pattern.

4

What version fixes the problem?

The issue is fixed in mport version 2.7.8. The correction resets optind and optreset before using the adjusted local arguments.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203