{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-54582 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-54582 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-54582 is a medium-severity path traversal vulnerability in MidnightBSD mport, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-54582 and fix it if it is affected.\n\nWhat it is: CVE-2026-54582 is a medium-severity path traversal vulnerability in MidnightBSD mport, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-54582 in the wild and no public exploit code.\n\nAffected product: MidnightBSD mport. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-54582/ (Markdown: https://insights.sbomify.com/CVE-2026-54582/index.md)","id":"CVE-2026-54582","markdown":"https://insights.sbomify.com/CVE-2026-54582/index.md","name":"CVE-2026-54582","record":{"aliases":["GHSA-5773-7r4r-rpgx"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["data_modify","privilege_escalation"],"network_reachable":"yes","non_default_config":true,"product_category":"MidnightBSD package manager","requires_auth":"none","summary":"A crafted package can overwrite existing files during installation if force mode is enabled, compromising filesystem integrity and potentially allowing privilege escalation.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-73","name":"External Control of File Name or Path"},{"id":"CWE-668","name":"Exposure of Resource to Wrong Sphere"}],"description":"mport is the MidnightBSD Package Manager. Prior to 2.7.8, package installation lacked a preflight check for incoming non-directory assets that already existed on disk. The affected logic across libmport/check_preconditions.c, libmport/install_primative.c, and libmport/mport_private.h did not apply MPORT_PRECHECK_FILE_CONFLICTS, so a crafted or conflicting package could overwrite a file owned by another package or unmanaged by mport. The check is bypassed only when the operator explicitly enables mport-\u003eforce. Privileged installation without that override could compromise local filesystem integrity and package database consistency. This issue is fixed in version 2.7.8.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"mport package installation can overwrite existing unmanaged or differently owned files","id":"CVE-2026-54582","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"mport package bundle downloads allow unsafe destination filenames","id":"CVE-2026-54583"},"packages":[],"prev":{"headline":"mport bootstrap index fetch can continue after hash verification failure","id":"CVE-2026-54581"},"products":["mport"],"published":"2026-09-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-17","vendors":["MidnightBSD"]},"summary":"A crafted package can overwrite existing files during installation if force mode is enabled, compromising filesystem integrity and potentially allowing privilege escalation.","url":"https://insights.sbomify.com/CVE-2026-54582/"}