{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-95848 exists.","fix":"No fix has been published for CVE-2026-95848 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-95848 is a critical authentication bypass 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-95848 and fix it if it is affected.\n\nWhat it is: CVE-2026-95848 is a critical authentication bypass 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-95848 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-95848/ (Markdown: https://insights.sbomify.com/CVE-2026-95848/index.md)","id":"CVE-2026-95848","markdown":"https://insights.sbomify.com/CVE-2026-95848/index.md","name":"CVE-2026-95848","record":{"aliases":[],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Java MQTT broker","requires_auth":"none","summary":"Moquette MQTT broker fails open to allow all access if configured authentication or authorization classes fail to load, bypassing security controls.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"moquette","vendor":"moquette"}],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-636","name":"Not Failing Securely"}],"description":"Moquette is a lightweight Java MQTT broker. Prior to 0.18.1, when a configured authenticator or authorizator class cannot be loaded, Server.initializeAuthenticator and Server.initializeAuthorizatorPolicy treat the failure as though no custom class was configured and fall back to AcceptAllAuthenticator or PermitAllAuthorizatorPolicy. A misspelled class name, missing dependency, constructor failure, or classpath problem can therefore start the broker with authentication or authorization disabled even though the operator configured those controls. 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 fails open when configured authentication or authorization classes cannot load","id":"CVE-2026-95848","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"libp2p-rust: Gossipsub GRAFT topics unbounded growth","id":"CVE-2026-95859"},"packages":[],"prev":{"headline":"Moquette client IDs can cause cross-session H2 durable-queue corruption","id":"CVE-2026-95847"},"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":8.8,"headline":"Moquette client IDs can cause cross-session H2 durable-queue corruption","id":"CVE-2026-95847","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":"total"},"state":"PUBLISHED","updated":"2026-09-23","vendors":["moquette-io"]},"summary":"Moquette MQTT broker fails open to allow all access if configured authentication or authorization classes fail to load, bypassing security controls.","url":"https://insights.sbomify.com/CVE-2026-95848/"}