{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34608 exists.","fix":"No fix has been published for CVE-2026-34608 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-34608 is a medium-severity memory corruption vulnerability in nanomq, published on 2 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-34608 and fix it if it is affected.\n\nWhat it is: CVE-2026-34608 is a medium-severity memory corruption vulnerability in nanomq, published on 2 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34608 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-34608/ (Markdown: https://insights.sbomify.com/CVE-2026-34608/index.md)","id":"CVE-2026-34608","markdown":"https://insights.sbomify.com/CVE-2026-34608/index.md","name":"CVE-2026-34608","record":{"aliases":["GHSA-8p57-jxj9-3qq3"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"NanoMQ MQTT Broker","requires_auth":"high_privilege","summary":"An out-of-bounds read in NanoMQ's webhook processing allows attackers to cause crashes or potentially execute code via crafted JSON payloads.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"nanomq","vendor":"emqx"}],"cvss":{"score":4.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-457","name":"Use of Uninitialized Variable"},{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"NanoMQ MQTT Broker (NanoMQ) is an all-around Edge Messaging Platform. Prior to version 0.24.10, in NanoMQ's webhook_inproc.c, the hook_work_cb() function processes nng messages by parsing the message body with cJSON_Parse(body). The body is obtained from nng_msg_body(msg), which is a binary buffer without a guaranteed null terminator. This leads to an out-of-bounds read (OOB read) as cJSON_Parse reads until it finds a \\0, potentially accessing memory beyond the allocated buffer (e.g., nng_msg metadata or adjacent heap/stack). The issue is often masked by nng's allocation padding (extra 32 bytes of zeros for non-power-of-two sizes \u003c1024 or non-aligned). The overflow is reliably triggered when the JSON payload length is a power-of-two \u003e=1024 (no padding added). This issue has been patched in version 0.24.10.","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: Heap-Buffer-Overflow in webhook_inproc.c via cJSON_Parse OOB Read","id":"CVE-2026-34608","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"leancrypto: Integer truncation in X.509 name parser enables certificate identity impersonation","id":"CVE-2026-34610"},"packages":[],"prev":{"headline":"Emlog: Path Traversal in emUnZip() allows arbitrary file write leading to RCE","id":"CVE-2026-34607"},"products":["nanomq"],"published":"2026-04-02","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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-02","vendors":["nanomq"]},"summary":"An out-of-bounds read in NanoMQ's webhook processing allows attackers to cause crashes or potentially execute code via crafted JSON payloads.","url":"https://insights.sbomify.com/CVE-2026-34608/"}