{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-85443 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-85443 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-85443 is a high-severity denial of service vulnerability in themoos core-moos, 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-85443 and fix it if it is affected.\n\nWhat it is: CVE-2026-85443 is a high-severity denial of service vulnerability in themoos core-moos, 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-85443 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-85443/ (Markdown: https://insights.sbomify.com/CVE-2026-85443/index.md)","id":"CVE-2026-85443","markdown":"https://insights.sbomify.com/CVE-2026-85443/index.md","name":"CVE-2026-85443","record":{"aliases":["GHSA-qqc5-c4q6-4q3x"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"MOOS middleware","requires_auth":"none","summary":"An attacker can cause a denial of service in MOOSDB by opening a TCP connection and sending no data, blocking the accept thread.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"core-moos","vendor":"themoos"}],"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-400","name":"Uncontrolled Resource Consumption"}],"description":"MOOS core-moos through 10.4.0 contains a denial of service vulnerability in MOOSCommServer::ListenLoop() where the accept thread performs a blocking receive without timeout during the wire-protocol handshake. An attacker can open a TCP connection to the MOOSDB port and send no data, causing the accept thread to block indefinitely while holding the socket-list lock, preventing all subsequent client connections.","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 MOOSDB Accept Loop Denial of Service","id":"CVE-2026-85443","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 Out-of-Bounds Read in isBraced, isQuoted and isChevroned","id":"CVE-2026-85444"},"packages":[],"prev":{"headline":"MOOS core-moos through 10.4.0 MOOSDB Denial of Service via Unbounded Packet Allocation","id":"CVE-2026-85442"},"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-14","vendors":["themoos"]},"summary":"An attacker can cause a denial of service in MOOSDB by opening a TCP connection and sending no data, blocking the accept thread.","url":"https://insights.sbomify.com/CVE-2026-85443/"}