{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45151 exists.","fix":"No fix has been published for CVE-2026-45151 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-45151 is a low-severity vulnerability in nanomq, published on 29 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-45151 and fix it if it is affected.\n\nWhat it is: CVE-2026-45151 is a low-severity vulnerability in nanomq, published on 29 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45151 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-45151/ (Markdown: https://insights.sbomify.com/CVE-2026-45151/index.md)","id":"CVE-2026-45151","markdown":"https://insights.sbomify.com/CVE-2026-45151/index.md","name":"CVE-2026-45151","record":{"aliases":["GHSA-9qhf-wgp4-p7w5"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"MQTT broker","requires_auth":"none","summary":"A null pointer dereference in NanoMQ's QUIC stream handling allows attackers to cause a denial of service by triggering a specific state condition.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":2.9,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-476","name":"NULL Pointer Dereference"}],"description":"NanoMQ MQTT Broker (NanoMQ) is an all-around Edge Messaging Platform. In 0.24.8 and earlier, quic_stream_recv can dereference a null substream pointer when a substream is in reopen state. The code finishes the AIO with error but does not return before locking c-\u003emtx.","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","id":"CVE-2026-45151","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":"uniget: Command Injection in tool.Check Leading to Arbitrary Code Execution","id":"CVE-2026-45152"},"packages":[],"prev":{"headline":"Zen Browser - Missing Fullscreen Security Notification Allows Origin Spoofing","id":"CVE-2026-45150"},"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-06-01","vendors":["nanomq"]},"summary":"A null pointer dereference in NanoMQ's QUIC stream handling allows attackers to cause a denial of service by triggering a specific state condition.","url":"https://insights.sbomify.com/CVE-2026-45151/"}