cve.bz

CVE-2026-67416 rabbitmq rabbitmq-server: Uncaught Exception

5.3 mediumEPSS 0.6%

Medium (5.3) in rabbitmq rabbitmq-server. EPSS 0.6% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

5.3 medium
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
EPSS
0.6% (unchanged from 0.6% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 50th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-10-15. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-20 Improper Input Validation
CWE-248 Uncaught Exception
CWE-754 Improper Check for Unusual or Exceptional Conditions
OWASP Top 10
A05:2025 Injection, A10:2025 Mishandling of Exceptional Conditions
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-67416 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-67416?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-67416?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-67416 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
rabbitmq-server>= 4.0.0, < 4.0.24
rabbitmq-server>= 4.1.0, < 4.1.15
rabbitmq-server>= 4.2.0, < 4.2.10
rabbitmq-server>= 4.3.0, < 4.3.4

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13rabbitmq-serverno fix listedDEBIAN-CVE-2026-67416
Debian14rabbitmq-server4.3.6-1DEBIAN-CVE-2026-67416
Ubuntu22.04:LTS, 24.04:LTS, 26.04:LTS and 4 morerabbitmq-serverno fix listedUBUNTU-CVE-2026-67416
Red Hathummingbird:1rabbitmq-server4.30:4.3.6-1.1.hum1RHSA-2026:82703

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is evaluated as a Moderate severity flaw because successful exploitation requires an authenticated client holding write authorization and does not compromise the broker itself or bypass access controls. While a malicious publisher can cause client-side disruptions or terminate cross-protocol decoding worker processes, the core messaging daemon maintains routing integrity and system confidentiality remains unaffected. In typical Red Hat deployments, older RabbitMQ releases packaged in supported legacy platforms do not incorporate the affected AMQP 1.0 parsing logic, restricting impact to environments running newer broker streams.

ProductPackageStateAdvisory
Red Hat Hardened Imagesrabbitmq-server4-3-main-4.3.6-1.1.hum1Fixed 2026-10-14RHSA-2026:82703
Red Hat Hardened Imagesrabbitmq-server4.2Will not fix
Red Hat OpenStack Platform 13 (Queens)rabbitmq-serverOut of support scope
Red Hat OpenStack Platform 16.2rabbitmq-serverOut of support scope
Red Hat OpenStack Platform 17.1rabbitmq-serverOut of support scope
Red Hat OpenStack Platform 18.0rabbitmq-serverFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-67416.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).

References

Check your stackJSON