{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44640 exists.","fix":"No fix has been published for CVE-2026-44640 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-44640 is a medium-severity memory corruption vulnerability in nanomq, published on 29 May 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-44640 and fix it if it is affected.\n\nWhat it is: CVE-2026-44640 is a medium-severity memory corruption vulnerability in nanomq, published on 29 May 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44640 exists.\n\nAffected product: nanomq. 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-44640/ (Markdown: https://insights.sbomify.com/CVE-2026-44640/index.md)","id":"CVE-2026-44640","markdown":"https://insights.sbomify.com/CVE-2026-44640/index.md","name":"CVE-2026-44640","record":{"aliases":["GHSA-9fgw-v323-jmjj"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"NanoMQ MQTT Broker","requires_auth":"none","summary":"A type confusion in NanoMQ's QUIC dialer close path can cause a hang or crash, leading to denial of service.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-843","name":"Access of Resource Using Incompatible Type"}],"description":"NanoMQ MQTT Broker (NanoMQ) is an all-around Edge Messaging Platform. Prior to 0.24.14, aio-\u003eprov_data is stored as nni_quic_conn* during dialing, but read as ex_quic_conn* during dialer close. This type confusion causes invalid object interpretation and leads to close-path hang/crash behavior. This vulnerability is fixed in 0.24.14.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"NanoMQ: QUIC Dialer Close Type Confusion","id":"CVE-2026-44640","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Microsoft APM: plugin.json component paths escape plugin root and copy arbitrary host files during install","id":"CVE-2026-44641"},"packages":[],"prev":{"headline":"NanoMQ: O(N²) Denial of Service in MQTT v5 Property Parsing","id":"CVE-2026-44639"},"products":["nanomq"],"published":"2026-05-29","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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-29","vendors":["nanomq"]},"summary":"A type confusion in NanoMQ's QUIC dialer close path can cause a hang or crash, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2026-44640/"}