{"answers":{"affected":"1 open source package ship an affected version, including rabbitmq.","exploited":"There is no known exploitation of CVE-2026-67418 in the wild and no public exploit code.","fix":"Upgrade rabbitmq to a fixed version for your release line: 3.13.19, 4.0.24, 4.1.15 or 4.2.10.","what":"CVE-2026-67418 is a medium-severity denial of service vulnerability in rabbitmq-server, published on 14 Oct 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-67418 and fix it if it is affected.\n\nWhat it is: CVE-2026-67418 is a medium-severity denial of service vulnerability in rabbitmq-server, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-67418 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- rabbitmq (Bitnami): affected from 3.13.0; fixed in 3.13.19, 4.0.24, 4.1.15, 4.2.10, 4.3.5\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-67418/ (Markdown: https://insights.sbomify.com/CVE-2026-67418/index.md)","id":"CVE-2026-67418","markdown":"https://insights.sbomify.com/CVE-2026-67418/index.md","name":"CVE-2026-67418","record":{"aliases":["AZL-108480","BIT-rabbitmq-2026-67418","DEBIAN-CVE-2026-67418","GHSA-jv99-v328-mvmm","UBUNTU-CVE-2026-67418"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"RabbitMQ message broker","requires_auth":"low_privilege","summary":"An authenticated publisher can disconnect matching MQTT subscribers by sending invalid properties, causing a denial of service for those subscribers.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-248","name":"Uncaught Exception"},{"id":"CWE-1286","name":"Improper Validation of Syntactic Correctness of Input"}],"description":"RabbitMQ is a messaging and streaming broker. From 3.13.0 until 3.13.19, 4.0.24, 4.1.15, 4.2.10, and 4.3.5, the MQTT 5 parser in deps/rabbitmq_mqtt/src/rabbit_mqtt_packet.erl accepts Request-Problem-Information on PUBLISH packets even though the property is valid only for CONNECT. An authenticated publisher with topic write permission can cause the broker to store and route that inapplicable property to a separately authenticated matching subscriber. When the subscriber path serializes the outbound PUBLISH, serialise_prop/2 has no matching clause, and the uncontained function_clause exception closes the victim MQTT or Web MQTT connection. The publisher connection and broker remain available, and queued replay, retained-message persistence, and broker-wide denial of service were not established. This issue is fixed in versions 3.13.19, 4.0.24, 4.1.15, 4.2.10, and 4.3.5.","ecosystems":["Bitnami"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"RabbitMQ MQTT 5: inapplicable PUBLISH property disconnects matching subscribers","id":"CVE-2026-67418","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":1,"n_references":6,"next":{"headline":"RabbitMQ: Consecutive topic wildcards cause combinatorial routing work","id":"CVE-2026-67419"},"packages":[{"ecosystem":"Bitnami","fixed":["3.13.19","4.0.24","4.1.15","4.2.10","4.3.5"],"introduced":["3.13.0","4.0.0","4.1.0","4.2.0","4.3.0"],"last_affected":[],"package":"rabbitmq","purl":"pkg:bitnami/rabbitmq","source":"BIT-rabbitmq-2026-67418"}],"prev":{"headline":"RabbitMQ: AMQP 1.0 symbolic body descriptor prefix collisions bypass validation","id":"CVE-2026-67416"},"products":["rabbitmq-server"],"published":"2026-10-14","related":[],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-14","vendors":["rabbitmq"]},"summary":"An authenticated publisher can disconnect matching MQTT subscribers by sending invalid properties, causing a denial of service for those subscribers.","url":"https://insights.sbomify.com/CVE-2026-67418/"}