---
id: CVE-2026-67416
title: RabbitMQ is a messaging and streaming broker
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,…
severity: none
cwe:
  - CWE-20
  - CWE-248
  - CWE-754
published: '2026-10-14'
updated: '2026-10-14'
sourceUpdated: '2026-10-14T16:17:50.843'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-67416'
references:
  - url: >-
      https://github.com/rabbitmq/rabbitmq-server/commit/c9b4b10c2dbf0f1c89f10b482ac8b45f84dc5954
    label: security-advisories@github.com
  - url: >-
      https://github.com/rabbitmq/rabbitmq-server/commit/d5186e66e056960f58e2d0fbee2fcc66e1ed6fb9
    label: security-advisories@github.com
  - url: 'https://github.com/rabbitmq/rabbitmq-server/pull/17017'
    label: security-advisories@github.com
  - url: 'https://github.com/rabbitmq/rabbitmq-server/pull/17287'
    label: security-advisories@github.com
  - url: 'https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.4'
    label: security-advisories@github.com
  - url: >-
      https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-p35w-6mx2-q4pc
    label: security-advisories@github.com
tags:
  - nvd
ingestedAt: '2026-10-14T16:40:32.127Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.