# CVE-2026-54578: mport verify can compare stale checksum data after hashing failures

> Attackers can bypass package integrity checks by causing hashing failures, allowing malicious packages to appear valid in MidnightBSD.

- **Severity:** Low 2.0 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Sep 2026
- **Updated:** 18 Sep 2026
- **Also known as:** GHSA-hgmr-9p75-q5cg

## What is CVE-2026-54578?

CVE-2026-54578 is a low-severity vulnerability in MidnightBSD mport, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

mport is the MidnightBSD Package Manager. Prior to 2.7.8, mport_verify_package() in libmport/verify.c could continue after MD5File() or SHA256_File() failed and compare an expected checksum with stale data in the hash buffer rather than a newly computed digest. An attacker able to influence an installed file or the conditions that make hashing fail could receive a misleading integrity result or hide a checksum failure. This issue is fixed in version 2.7.8.

Weakness: CWE-755 (Improper Handling of Exceptional Conditions), CWE-354 (Improper Validation of Integrity Check Value)

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


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

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

## Is CVE-2026-54578 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-54578 is a low-severity vulnerability in MidnightBSD mport, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-54578 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-54578/ (Markdown: https://insights.sbomify.com/CVE-2026-54578/index.md)
```

## Sources

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

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