Index corruption and service interruption via zstd failures
Published Sep 17, 2026 · Updated Sep 24, 2026
Improper zstd error handling in MidnightBSD Mport before 2.7.8 allows remote attackers to corrupt package indexes or interrupt service. The mport_decompress_zstd() path accepted incomplete streams or failed writes without always removing partial output, while index-fetch callers ignored some failures. Exploitation requires control of compressed index content served by a package mirror; the bounded result is index-integrity loss or package-management interruption.
Summary
What happened
Improper zstd error handling in MidnightBSD Mport before 2.7.8 allows remote attackers to corrupt package indexes or interrupt service. The mport_decompress_zstd() path accepted incomplete streams or failed writes without always removing partial output, while index-fetch callers ignored some failures. Exploitation requires control of compressed index content served by a package mirror; the bounded result is index-integrity loss or package-management interruption.
The record
- CVE
- CVE-2026-54580
- Published
- Sep 17, 2026
- Updated
- Sep 24, 2026
- Vendor
- MidnightBSD
- Product
- Mport
- Classifications
- CWE-755, CWE-354
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 17, 2026CVE publishedPublication date reported by the CVE source.
- Sep 24, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.7.8
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started