{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47275 exists.","fix":"No fix has been published for CVE-2026-47275 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-47275 is a low-severity vulnerability in nanomq, published on 20 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-47275 and fix it if it is affected.\n\nWhat it is: CVE-2026-47275 is a low-severity vulnerability in nanomq, published on 20 Jul 2026. Any signed-in user can exploit it over the 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-47275 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-47275/ (Markdown: https://insights.sbomify.com/CVE-2026-47275/index.md)","id":"CVE-2026-47275","markdown":"https://insights.sbomify.com/CVE-2026-47275/index.md","name":"CVE-2026-47275","record":{"aliases":["GHSA-52qr-3v49-wmx6"],"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":"A malicious MQTT broker can crash NanoMQ clients via a NULL pointer dereference in the CONNECT decoder, causing remote denial of service.","user_interaction":"required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":2.6,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:L","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 `nni_mqttv5_msg_decode_connect()` allows a malicious MQTT broker to crash any connecting NanoMQ MQTTv5 client (including bridge mode) with a single packet, causing remote denial of service via SIGSEGV. In `nni_mqttv5_msg_decode_connect()` (`mqtt_codec.c:1863`), the code iterates over CONNECT properties using variable `prop` when it should use `will_prop`. When a CONNECT packet has no connect-level properties (`prop == NULL`) but has will properties (`will_prop != NULL`), dereferencing `prop-\u003enext` causes SIGSEGV at address `0x38` (NULL + `offsetof(property, next)`).\n\nThis affects both `nanomq_cli` and **NanoMQ bridge mode** (Core component), as both use the same `mqtt_client.c` receive path. This can lead to remote DoS if a malicious MQTT broker can crash the client process with a single 35-byte packet and persistent DoS if auto-reconnect causes infinite crash loop.","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 NULL Pointer Dereference in MQTTv5 Client CONNECT Decoder Leading to Remote DoS","id":"CVE-2026-47275","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":"NULL Pointer Dereference in REST API properties_parse via Malformed user_properties","id":"CVE-2026-47276"},"packages":[],"prev":{"headline":"pam_usb: Uncontrolled search path in pam_usb tools allows privilege escalation via PATH manipulation","id":"CVE-2026-47274"},"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":"A malicious MQTT broker can crash NanoMQ clients via a NULL pointer dereference in the CONNECT decoder, causing remote denial of service.","url":"https://insights.sbomify.com/CVE-2026-47275/"}