{"answers":{"affected":"1 open source package ship an affected version, including rabbitmq.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67416 exists.","fix":"Upgrade rabbitmq to a fixed version for your release line: 4.0.24, 4.1.15, 4.2.10 or 4.3.4.","what":"CVE-2026-67416 is a medium-severity vulnerability in rabbitmq-server, published on 14 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-67416 and fix it if it is affected.\n\nWhat it is: CVE-2026-67416 is a medium-severity vulnerability in rabbitmq-server, published on 14 Oct 2026. \nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67416 exists.\n\nAffected packages and fixed versions:\n- rabbitmq (Bitnami): affected from 4.0.0; fixed in 4.0.24, 4.1.15, 4.2.10, 4.3.4\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-67416/ (Markdown: https://insights.sbomify.com/CVE-2026-67416/index.md)","id":"CVE-2026-67416","markdown":"https://insights.sbomify.com/CVE-2026-67416/index.md","name":"CVE-2026-67416","record":{"aliases":["BIT-rabbitmq-2026-67416","DEBIAN-CVE-2026-67416","GHSA-p35w-6mx2-q4pc","UBUNTU-CVE-2026-67416"],"analysis":null,"analysis_generated_by":null,"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-754","name":"Improper Check for Unusual or Exceptional Conditions"},{"id":"CWE-248","name":"Uncaught Exception"},{"id":"CWE-20","name":"Improper Input Validation"}],"description":"RabbitMQ is a messaging and streaming broker. From 4.0.0 until 4.0.24, 4.1.15, 4.2.10, and 4.3.4, the optimized AMQP 1.0 server_mode parser in deps/amqp10_common/src/amqp10_binary_parser.erl matches the textual prefixes of symbolic data, sequence, and value body descriptors without verifying their encoded symbol lengths. An authenticated AMQP 1.0 publisher with write permission can submit a well-formed unknown descriptor that begins with a registered body descriptor, and RabbitMQ misclassifies and stores the bytes as a standard body section. Strict AMQP 1.0 consumers can terminate while decoding the stored entry. For bodies misclassified as data, AMQP 0-9-1 or other cross-protocol conversion performs full body decoding and can terminate the consumer protocol process, with acknowledgement-required delivery permitting repeated failures. Sequence and value classifications are normally transported as opaque encoded payloads on that conversion path. The broker remains alive, and the issue does not bypass routing or authorization. This issue is fixed in versions 4.0.24, 4.1.15, 4.2.10, and 4.3.4.","ecosystems":["Bitnami"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"RabbitMQ: AMQP 1.0 symbolic body descriptor prefix collisions bypass validation","id":"CVE-2026-67416","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":null,"year":"2026"},"n_packages":1,"n_references":6,"next":{"headline":"RabbitMQ MQTT 5: inapplicable PUBLISH property disconnects matching subscribers","id":"CVE-2026-67418"},"packages":[{"ecosystem":"Bitnami","fixed":["4.0.24","4.1.15","4.2.10","4.3.4"],"introduced":["4.0.0","4.1.0","4.2.0","4.3.0"],"last_affected":[],"package":"rabbitmq","purl":"pkg:bitnami/rabbitmq","source":"BIT-rabbitmq-2026-67416"}],"prev":{"headline":"RabbitMQ: Shovel Management Atom Exhaustion Allows Persistent Broker-Wide Denial of Service","id":"CVE-2026-67415"},"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-15","vendors":["rabbitmq"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-67416/"}