{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-85445 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-85445 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-85445 is a high-severity denial of service vulnerability in moos-ivp, published on 3 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-85445 and fix it if it is affected.\n\nWhat it is: CVE-2026-85445 is a high-severity denial of service vulnerability in moos-ivp, published on 3 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-85445 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-85445/ (Markdown: https://insights.sbomify.com/CVE-2026-85445/index.md)","id":"CVE-2026-85445","markdown":"https://insights.sbomify.com/CVE-2026-85445/index.md","name":"CVE-2026-85445","record":{"aliases":["GHSA-8cvc-f53x-r3v4"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"MOOS-IvP library","requires_auth":"none","summary":"Attackers can cause denial of service in MOOS-IvP by sending mux packets with large declared counts, triggering unbounded memory allocation.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"moos-ivp","vendor":"mit"}],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-789","name":"Memory Allocation with Excessive Size Value"}],"description":"MOOS-IvP through 24.8.1 contains a denial of service vulnerability in the Demuxer::addMuxPacket() function that trusts the packet count declared in mux headers without validation. Attackers can declare arbitrarily large packet counts to trigger unbounded memory allocation, exhausting system resources and causing service unavailability.","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 BHV_IPF Demultiplexer Memory Exhaustion via Packet Count","id":"CVE-2026-85445","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"MOOS-IvP through 24.8.1 uFldNodeComms Quadratic Processing Denial of Service","id":"CVE-2026-85446"},"packages":[],"prev":{"headline":"MOOS-IvP through 24.8.1 Out-of-Bounds Read in isBraced, isQuoted and isChevroned","id":"CVE-2026-85444"},"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-04","vendors":["moos-ivp"]},"summary":"Attackers can cause denial of service in MOOS-IvP by sending mux packets with large declared counts, triggering unbounded memory allocation.","url":"https://insights.sbomify.com/CVE-2026-85445/"}