{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47276 exists.","fix":"No fix has been published for CVE-2026-47276 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-47276 is a medium-severity vulnerability in nanomq, published on 20 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-47276 and fix it if it is affected.\n\nWhat it is: CVE-2026-47276 is a medium-severity vulnerability in nanomq, published on 20 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47276 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-47276/ (Markdown: https://insights.sbomify.com/CVE-2026-47276/index.md)","id":"CVE-2026-47276","markdown":"https://insights.sbomify.com/CVE-2026-47276/index.md","name":"CVE-2026-47276","record":{"aliases":["GHSA-qq2v-xvxg-3hvf"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"NanoMQ MQTT broker","requires_auth":"low_privilege","summary":"An authenticated attacker can crash the NanoMQ broker by sending a malformed JSON array in user_properties to the publish API endpoint.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-476","name":"NULL Pointer Dereference"}],"description":"In nanomq versions 0.24.11 and earlier, a NULL pointer dereference in `properties_parse()` allows an authenticated attacker to crash the NanoMQ broker by sending a POST request to `/api/v4/mqtt/publish` with `user_properties` as a JSON array instead of a JSON object. The crash occurs because `strlen()` is called on a NULL `item-\u003estring` pointer when iterating over array elements. An authenticated attacker can exploit this to crash the NanoMQ broker process. This is patched in version 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":"NULL Pointer Dereference in REST API properties_parse via Malformed user_properties","id":"CVE-2026-47276","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Runtipi: Unauthenticated arbitrary file read through app-store logo symlinks","id":"CVE-2026-47277"},"packages":[],"prev":{"headline":"nanomq NULL Pointer Dereference in MQTTv5 Client CONNECT Decoder Leading to Remote DoS","id":"CVE-2026-47275"},"products":["nanomq"],"published":"2026-07-20","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-07-20","vendors":["nanomq"]},"summary":"An authenticated attacker can crash the NanoMQ broker by sending a malformed JSON array in user_properties to the publish API endpoint.","url":"https://insights.sbomify.com/CVE-2026-47276/"}