{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-85451 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-85451 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-85451 is a high-severity vulnerability in themoos core-moos, published on 3 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-85451 and fix it if it is affected.\n\nWhat it is: CVE-2026-85451 is a high-severity vulnerability in themoos core-moos, published on 3 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-85451 in the wild and no public exploit code.\n\nAffected product: themoos core-moos. 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-85451/ (Markdown: https://insights.sbomify.com/CVE-2026-85451/index.md)","id":"CVE-2026-85451","markdown":"https://insights.sbomify.com/CVE-2026-85451/index.md","name":"CVE-2026-85451","record":{"aliases":["GHSA-wgxw-v27j-4ppq"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"MOOS middleware library","requires_auth":"none","summary":"Attackers can remotely terminate MOOS processes by exploiting a hard-coded multicast passphrase, causing denial of service.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"core-moos","vendor":"themoos"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"MOOS core-moos through 10.4.0 contains a remote process termination vulnerability in the SuicidalSleeper component that uses a hard-coded passphrase for multicast command authorization. Any multicast-reachable peer can enumerate MOOS processes and send termination commands to trigger process shutdown by exploiting the default multicast group and port with the known passphrase.","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 core-moos through 10.4.0 Remote Process Termination via Hard-Coded Multicast Passphrase","id":"CVE-2026-85451","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"MOOS ui-moos through 50b9c6c uMS Buffer Overflow via Long MOOS Identifiers","id":"CVE-2026-85452"},"packages":[],"prev":{"headline":"MOOS core-moos through 10.4.0 MOOSDB HTTP Server Resource Exhaustion","id":"CVE-2026-85450"},"products":["core-moos"],"published":"2026-09-03","related":[{"cvss_score":9.3,"headline":"MOOS core-moos through 10.4.0 Missing Authentication for MOOSDB Publish, Subscribe and DB_CLEAR","id":"CVE-2026-85424","kev_date_added":null,"published":"2026-09-03"},{"cvss_score":9.3,"headline":"MOOS core-moos through 10.4.0 MOOSDB HTTP Server Unauthenticated Variable Write","id":"CVE-2026-85428","kev_date_added":null,"published":"2026-09-03"},{"cvss_score":9.3,"headline":"MOOS core-moos through 10.4.0 MOOSDB Pre-Authentication Heap Overflow via Negative Packet Length","id":"CVE-2026-85440","kev_date_added":null,"published":"2026-09-03"},{"cvss_score":8.8,"headline":"MOOS core-moos through 10.4.0 MOOSDB Message Source Spoofing via Wire Identity","id":"CVE-2026-85432","kev_date_added":null,"published":"2026-09-03"},{"cvss_score":8.8,"headline":"MOOS core-moos through 10.4.0 MOOSDB Out-of-Bounds Read via Short Packet","id":"CVE-2026-85455","kev_date_added":null,"published":"2026-09-03"},{"cvss_score":8.7,"headline":"MOOS core-moos through 10.4.0 MOOSDB Denial of Service via Negative Serialized String Length","id":"CVE-2026-85441","kev_date_added":null,"published":"2026-09-03"},{"cvss_score":8.7,"headline":"MOOS core-moos through 10.4.0 MOOSDB Denial of Service via Unbounded Packet Allocation","id":"CVE-2026-85442","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":"partial"},"state":"PUBLISHED","updated":"2026-09-04","vendors":["themoos"]},"summary":"Attackers can remotely terminate MOOS processes by exploiting a hard-coded multicast passphrase, causing denial of service.","url":"https://insights.sbomify.com/CVE-2026-85451/"}