ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-67235

RabbitMQ: AMQP 0-9-1 body assembly never validates accumulated size

Published Sep 23, 2026 · catalog updated Sep 24, 2026 · RabbitMQ: AMQP 0-9-1 body

Check if you run it

No confirmed exploitation is on record for CVE-2026-67235. EPSS is 0.26%. Act only if a listed version of RabbitMQ: AMQP 0-9-1 body is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (RabbitMQ: AMQP 0-9-1 body).
  • No version range is stored. A customer cannot check an installed version against this record.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High7.1
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.26%
Remediation
Advisory link
Affected products
vendor rabbitmq rabbitmq-server

RabbitMQ is a messaging and streaming broker. Prior to versions 4.3.0, 4.2.6, 4.1.11, 4.0.20, and 3.13.15, The content-header BodySize (a uint64) was stored without validation against max_message_size. The size check ran only when assembly completed. By declaring body_size = 2^63-1 and then streaming fragments, a client ensured that check_msg_size never fired, so the accumulated body size went unbounded. A reader process accumulates memory until the memory alarm fires, degrading all publishers cluster-wide, or until the node runs out of memory. The memory alarm provides only partial mitigation, since it is reactive rather than preventive. AMQP 0-9-1 is the most widely used protocol, and any publisher can trigger this condition. Preconditions include Any authenticated AMQP 0-9-1 client with publish permission can exploit this.. This issue is fixed in versions 4.3.0, 4.2.6, 4.1.11, 4.0.20, and 3.13.15.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • vendor rabbitmq rabbitmq-serverversion unspecified

How to fix CVE-2026-67235

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-67235. EPSS is 0.26%. Act only if a listed version of RabbitMQ: AMQP 0-9-1 body is installed.

Which versions are affected?

Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-770: Allocation of Resources Without Limits or Throttling. EPSS 0.26%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Ubuntu security

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Sep 24, 2026 · CVE.org

    Updated

    RabbitMQ is a messaging and streaming broker. Prior to versions 4.3.0, 4.2.6, 4.1.11, 4.0.20, and 3.13.15, The content-header BodySize (a uint64) was stored without validation against max_message_size. The size check ran only when assembly completed. By declaring body_size = 2^63-1 and then streaming fragments, a client ensured that check_msg_size never fired, so the accumulated body size went unb

  2. Oct 15, 2026 · Ubuntu Security Notices

    Detected

    CVE-2026-67235 is listed by USN-8933-1: RabbitMQ Server vulnerabilities.

Sources

  • CVE.orgVulnerability recordCVE-2026-67235

    RabbitMQ is a messaging and streaming broker. Prior to versions 4.3.0, 4.2.6, 4.1.11, 4.0.20, and 3.13.15, The content-header BodySize (a uint64) was stored without validation against max_message_size. The size check ran only when assembly completed. By declaring body_size = 2^63

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-67235

    30-day exploitation probability 0.3%

    first.org
  • Ubuntu Security NoticesVendor advisoryCVE-2026-67235

    It was discovered that RabbitMQ Server incorrectly handled CORS wildcard origin configuration. An attacker could possibly use this issue to cause a cross-site request forgery attack. This issue only affected Ubuntu 18.04 LTS, Ubuntu 20.04 LTS, Ubuntu 22.04 LTS, Ubuntu 24.04 LTS,

    ubuntu.com

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.