{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-22040 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-22040 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-22040 is a medium-severity use after free vulnerability in nanomq, published on 4 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-22040 and fix it if it is affected.\n\nWhat it is: CVE-2026-22040 is a medium-severity use after free vulnerability in nanomq, published on 4 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-22040 in the wild and no public exploit code.\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-22040/ (Markdown: https://insights.sbomify.com/CVE-2026-22040/index.md)","id":"CVE-2026-22040","markdown":"https://insights.sbomify.com/CVE-2026-22040/index.md","name":"CVE-2026-22040","record":{"aliases":["GHSA-v57q-w88m-424r"],"analysis":{"component_type":"server_software","fix_type":"no_fix_stated","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"NanoMQ MQTT Broker","requires_auth":"none","summary":"Attackers can crash the NanoMQ MQTT broker by triggering heap corruption via specific traffic patterns, causing a denial of service.","user_interaction":"required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"nanomq","vendor":"emqx"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-416","name":"Use After Free"}],"description":"NanoMQ MQTT Broker (NanoMQ) is an all-around Edge Messaging Platform. In version 0.24.6, by generating a combined traffic pattern of high-frequency publishes and rapid reconnect/kick-out using the same ClientID and massive subscribe/unsubscribe jitter, it is possible to reliably trigger heap memory corruption in the Broker process, causing it to exit immediately with SIGABRT due to free(): invalid pointer. As of time of publication, no known patched versions are available.","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":"NanoMQ 0.24.6 Use-After-Free Leading to Heap Corruption and Broker Crash","id":"CVE-2026-22040","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"loggingredactor converts non-string types to string types in logs","id":"CVE-2026-22041"},"packages":[],"prev":{"headline":"Kyverno Cross-Namespace Privilege Escalation via Policy apiCall","id":"CVE-2026-22039"},"products":["nanomq"],"published":"2026-03-04","related":[{"cvss_score":8.8,"headline":"Missing authorization in n/a","id":"CVE-2024-42655","kev_date_added":null,"published":"2025-07-29"},{"cvss_score":8.5,"headline":"NanoMQ has Buffer Overflow","id":"CVE-2025-59947","kev_date_added":null,"published":"2025-12-15"},{"cvss_score":8,"headline":"Memory corruption in n/a","id":"CVE-2023-34488","kev_date_added":null,"published":"2023-06-12"},{"cvss_score":7.7,"headline":"NanoMQ has Heap Buffer Overflow in URI Parameter Parsing","id":"CVE-2026-32135","kev_date_added":null,"published":"2026-04-20"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2026-36590","kev_date_added":null,"published":"2026-07-15"},{"cvss_score":7.5,"headline":"MQTT v5 Variable Byte Integer parsing out-of-bounds: get_var_integer()","id":"CVE-2026-21888","kev_date_added":null,"published":"2026-03-11"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2024-48077","kev_date_added":null,"published":"2026-01-15"}],"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-03-05","vendors":["nanomq"]},"summary":"Attackers can crash the NanoMQ MQTT broker by triggering heap corruption via specific traffic patterns, causing a denial of service.","url":"https://insights.sbomify.com/CVE-2026-22040/"}