{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-95847 exists.","fix":"No fix has been published for CVE-2026-95847 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-95847 is a high-severity vulnerability in moquette-io moquette, published on 23 Sep 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-95847 and fix it if it is affected.\n\nWhat it is: CVE-2026-95847 is a high-severity vulnerability in moquette-io moquette, published on 23 Sep 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-95847 exists.\n\nAffected product: moquette-io moquette. 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-95847/ (Markdown: https://insights.sbomify.com/CVE-2026-95847/index.md)","id":"CVE-2026-95847","markdown":"https://insights.sbomify.com/CVE-2026-95847/index.md","name":"CVE-2026-95847","record":{"aliases":[],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"MQTT broker","requires_auth":"none","summary":"Attackers can corrupt MQTT message queues by crafting client IDs, leading to data leakage or loss in Moquette broker durable sessions.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"moquette","vendor":"moquette"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-99","name":"Improper Control of Resource Identifiers"}],"description":"Moquette is a lightweight Java MQTT broker. Prior to 0.18.1, H2PersistentQueue derives a session's message-map name as queue_ plus the client ID and its metadata-map name as queue_ plus the client ID plus _meta. A durable session whose client ID ends in _meta can therefore make its message map collide with another client's metadata map. The colliding sessions read and write the same H2 MVStore map with incompatible value types, which can corrupt queue head and tail data and cause message loss, misdelivery, failed queue reloads, or exposure of queued content across sessions. This issue is fixed in version 0.18.1.","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":"Moquette client IDs can cause cross-session H2 durable-queue corruption","id":"CVE-2026-95847","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Moquette fails open when configured authentication or authorization classes cannot load","id":"CVE-2026-95848"},"packages":[],"prev":{"headline":"Moquette publishes Last-Will messages without enforcing write authorization","id":"CVE-2026-95846"},"products":["moquette"],"published":"2026-09-23","related":[{"cvss_score":9.6,"headline":"Moquette pattern ACL wildcard injection allows cross-tenant authorization bypass","id":"CVE-2026-85724","kev_date_added":null,"published":"2026-09-23"},{"cvss_score":9.3,"headline":"Moquette fails open when configured authentication or authorization classes cannot load","id":"CVE-2026-95848","kev_date_added":null,"published":"2026-09-23"},{"cvss_score":8.7,"headline":"Moquette uncaught MQTT command exceptions can terminate shared session event loops","id":"CVE-2026-95842","kev_date_added":null,"published":"2026-09-23"},{"cvss_score":8.7,"headline":"Moquette malformed shared subscriptions can crash command processing","id":"CVE-2026-95843","kev_date_added":null,"published":"2026-09-23"},{"cvss_score":8.7,"headline":"Moquette deeply nested MQTT topics can cause stack exhaustion","id":"CVE-2026-95844","kev_date_added":null,"published":"2026-09-23"},{"cvss_score":8.7,"headline":"Moquette unbounded per-session message queues allow memory exhaustion","id":"CVE-2026-95845","kev_date_added":null,"published":"2026-09-23"}],"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-23","vendors":["moquette-io"]},"summary":"Attackers can corrupt MQTT message queues by crafting client IDs, leading to data leakage or loss in Moquette broker durable sessions.","url":"https://insights.sbomify.com/CVE-2026-95847/"}