Consumer crashes via symbolic descriptor prefix collisions
Published Oct 14, 2026 · Updated Oct 14, 2026
AMQP 1.0 parser DoS in RabbitMQ Server allows remote authenticated users to crash consumers via crafted symbolic descriptors. The server_mode parser in deps/amqp10_common/src/amqp10_binary_parser.erl ignores encoded symbol lengths when matching body descriptor prefixes, storing unknown descriptors as standard body sections. Exploitation requires publishing permission and a consumer that strictly decodes the entry or fully decodes misclassified data during protocol conversion; acknowledgement-required redelivery repeats failures, but the broker remains alive and routing and authorization remain enforced.
Summary
What happened
AMQP 1.0 parser DoS in RabbitMQ Server allows remote authenticated users to crash consumers via crafted symbolic descriptors. The server_mode parser in deps/amqp10_common/src/amqp10_binary_parser.erl ignores encoded symbol lengths when matching body descriptor prefixes, storing unknown descriptors as standard body sections. Exploitation requires publishing permission and a consumer that strictly decodes the entry or fully decodes misclassified data during protocol conversion; acknowledgement-required redelivery repeats failures, but the broker remains alive and routing and authorization remain enforced.
The record
- CVE
- CVE-2026-67416
- Published
- Oct 14, 2026
- Updated
- Oct 14, 2026
- Vendor
- RabbitMQ
- Product
- RabbitMQ Server
- Classifications
- CWE-248, CWE-20, CWE-754, T1499.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 14, 2026CVE publishedPublication date reported by the CVE source.
- Oct 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 4.0.0, < 4.0.24
- Affected versionversion=>= 4.1.0, < 4.1.15
- Affected versionversion=>= 4.2.0, < 4.2.10
- Affected versionversion=>= 4.3.0, < 4.3.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
- Upstream deterministic parser and conversion proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started