{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-85439 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-85439 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-85439 is a high-severity command injection vulnerability in moos-ivp, published on 3 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-85439 and fix it if it is affected.\n\nWhat it is: CVE-2026-85439 is a high-severity command injection vulnerability in moos-ivp, published on 3 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-85439 in the wild and no public exploit code.\n\nAffected product: moos-ivp. 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-85439/ (Markdown: https://insights.sbomify.com/CVE-2026-85439/index.md)","id":"CVE-2026-85439","markdown":"https://insights.sbomify.com/CVE-2026-85439/index.md","name":"CVE-2026-85439","record":{"aliases":["GHSA-fm2r-qmc4-5wf2"],"analysis":{"component_type":"other","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"MOOS-IvP robotics software","requires_auth":"none","summary":"Attackers can execute arbitrary commands by injecting shell metacharacters into log file pathnames or the --dir parameter in alogsplit.","user_interaction":"required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"moos-ivp","vendor":"mit"}],"cvss":{"score":8.5,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"MOOS-IvP through 24.8.1 contains a remote code execution vulnerability in alogsplit's SplitHandler::handlePreCheckSplitDir() function that fails to sanitize shell metacharacters in log file pathnames. Attackers can embed shell syntax in log file names or the --dir parameter to execute arbitrary commands with the privileges of the operator running alogsplit.","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":"MOOS-IvP through 24.8.1 alogsplit Command Injection via Input Pathname","id":"CVE-2026-85439","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"MOOS core-moos through 10.4.0 MOOSDB Pre-Authentication Heap Overflow via Negative Packet Length","id":"CVE-2026-85440"},"packages":[],"prev":{"headline":"MOOS-IvP through 24.8.1 Out-of-Bounds Write via Unvalidated IvP Payload Counts","id":"CVE-2026-85438"},"products":["moos-ivp"],"published":"2026-09-03","related":[{"cvss_score":9.3,"headline":"MOOS-IvP through 24.8.1 iSay Command Injection via SAY_MOOS","id":"CVE-2026-85425","kev_date_added":null,"published":"2026-09-03"},{"cvss_score":9.3,"headline":"MOOS-IvP through 24.8.1 uFldShoreBroker Bridge Route Injection via Unverified Node Ping","id":"CVE-2026-85434","kev_date_added":null,"published":"2026-09-03"},{"cvss_score":9.3,"headline":"MOOS-IvP through 24.8.1 uFldNodeBroker Unauthenticated Shore Route Enrollment","id":"CVE-2026-85435","kev_date_added":null,"published":"2026-09-03"},{"cvss_score":9.3,"headline":"MOOS-IvP through 24.8.1 Buffer Overflow in IvP Function String Decoders","id":"CVE-2026-85437","kev_date_added":null,"published":"2026-09-03"},{"cvss_score":9.3,"headline":"MOOS-IvP through 24.8.1 Out-of-Bounds Write via Unvalidated IvP Payload Counts","id":"CVE-2026-85438","kev_date_added":null,"published":"2026-09-03"},{"cvss_score":8.7,"headline":"MOOS-IvP through 24.8.1 uFldNodeComms Node Message Source Spoofing","id":"CVE-2026-85429","kev_date_added":null,"published":"2026-09-03"},{"cvss_score":8.7,"headline":"MOOS-IvP through 24.8.1 Out-of-Bounds Read in isBraced, isQuoted and isChevroned","id":"CVE-2026-85444","kev_date_added":null,"published":"2026-09-03"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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":"total"},"state":"PUBLISHED","updated":"2026-09-05","vendors":["moos-ivp"]},"summary":"Attackers can execute arbitrary commands by injecting shell metacharacters into log file pathnames or the --dir parameter in alogsplit.","url":"https://insights.sbomify.com/CVE-2026-85439/"}