{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-54583 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-54583 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-54583 is a high-severity path traversal vulnerability in MidnightBSD mport, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-54583 and fix it if it is affected.\n\nWhat it is: CVE-2026-54583 is a high-severity path traversal vulnerability in MidnightBSD mport, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-54583 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-54583/ (Markdown: https://insights.sbomify.com/CVE-2026-54583/index.md)","id":"CVE-2026-54583","markdown":"https://insights.sbomify.com/CVE-2026-54583/index.md","name":"CVE-2026-54583","record":{"aliases":["GHSA-mr62-mqwj-vhh3"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"MidnightBSD package manager","requires_auth":"none","summary":"Attackers can write package data to arbitrary locations via malicious index data due to missing filename validation in MidnightBSD's mport.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.3,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/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-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"mport is the MidnightBSD Package Manager. Prior to 2.7.8, libmport/fetch.c did not consistently reject empty, dot, dot-dot, or slash-containing bundle filenames before composing package download and write paths. Malicious package index data could place an unsafe value in indexEntry-\u003ebundlefile, and the missing is_valid_bundle_filename() checks allowed downloaded package data to be written outside the intended cache location or to an unsafe destination name. 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 bundle downloads allow unsafe destination filenames","id":"CVE-2026-54583","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 trusts environment-controlled temporary directories in privileged metadata extraction","id":"CVE-2026-54584"},"packages":[],"prev":{"headline":"mport package installation can overwrite existing unmanaged or differently owned files","id":"CVE-2026-54582"},"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":"Attackers can write package data to arbitrary locations via malicious index data due to missing filename validation in MidnightBSD's mport.","url":"https://insights.sbomify.com/CVE-2026-54583/"}