Skip to content
Fencer Vulns
medium 5.3

CVE-2026-67416 json

RabbitMQ: AMQP 1.0 symbolic body descriptor prefix collisions bypass validation

published 2026-10-14 25 d ago modified 2026-10-21 19 d ago also BIT-rabbitmq-2026-67416 , EUVD-2026-101294 , GHSA-p35w-6mx2-q4pc

cvss
5.3
version 4.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 50%
public exploits
0
none known

Summary

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.

Patch / fix

  • bitnami rabbitmq 4.0.24, 4.1.15, 4.2.10, 4.3.4
  • vmware rabbitmq 4.0.24, 4.1.15, 4.2.10, 4.3.4
  • pivotal_software rabbitmq 4.0.24, 4.1.15, 4.2.10, 4.3.4
  • rabbitmq-server Debian 14 4.3.6-1

debian advisories DEBIAN-CVE-2026-67416

  • rabbitmq-server4.3 hummingbird 1 4.3.6-1.1.hum1

red hat advisories RHSA-2026:82703

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-67416 updated cvss 4.3

rabbitmq-server: rabbitmq-server: Denial of Service via improper AMQP message descriptor validation

  • Red Hat Hardened Images rabbitmq-server4.2 4.2.9-0.3.hum1
    affected: no fix planned “Will not fix”
  • Red Hat OpenStack Platform 13 (Queens) rabbitmq-server Red Hat OpenStack Platform 16.2 rabbitmq-server Red Hat OpenStack Platform 17.1 rabbitmq-server
    affected: no fix planned “Out of support scope”
  • Red Hat OpenStack Platform 18.0 rabbitmq-server
    affected: no fix available “Fix deferred”
  • Red Hat Hardened Images rabbitmq-server4.3 4.3.6-1.1.hum1
    fixed: vendor fix RHSA-2026:82703

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
24 d ago

Exploit prediction

0.62% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-p35w-6mx2-q4pc referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 4.0 5.3 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
CNA 4.0 5.3 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Affected packages

ecosystem package affected fixed in
bitnami rabbitmq
>=4.0.0, <4.0.24
>=4.1.0, <4.1.15
>=4.2.0, <4.2.10
>=4.3.0, <4.3.4
4.0.24
4.1.15
4.2.10
4.3.4

Affected products

  • rabbitmq rabbitmq-server

Classification

Weakness
  • CWE-20 Improper Input Validation
  • CWE-248 Uncaught Exception
  • CWE-754 Improper Check for Unusual or Exceptional Conditions

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.