Read the docs
TI-2026-47541 Aliases CVE-2026-67225

RabbitMQ: Stream-protocol frame length never validated against frame_max

Priority LOW 28CWE-770Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Attack requirements
Present
Impact type
Denial of service
Confidentiality · integrity · availability
None · None · Low
Fix status
Partial Red Hat: 1 fixed, 5 without a fix

Attack profile from CVSS 4.0 · CNA. Fix status from CNA and Red Hat. Impact type from CWE-770.

Summary

RabbitMQ is a messaging and streaming broker. From 3.13.0 until 3.13.15, 4.0.20, 4.1.11, and 4.2.6, the stream protocol stored the FrameMax value negotiated during the Tune handshake but did not compare it with an inbound frame's declared length before buffering the frame. With the stream plugin enabled, a remote client could therefore cause excessive memory pressure and denial of service by declaring an oversized frame. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00343 28th percentileScored 2026-11-07
Fix Partial rabbitmq-server (rabbitmq): 3.13.15, 4.0.20, 4.1.11 +1Red Hat: 1 advisoryRed Hat: 1 fixed, 5 without a fix

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
rabbitmqrabbitmq-server3.13.0 to before 3.13.15; 4.0.0 to before 4.0.20; 4.1.0 to before 4.1.11; 4.2.0 to before 4.2.63.13.15, 4.0.20, 4.1.11, 4.2.6Patch availableCNA
  • rabbitmq-server Vendorrabbitmq Affected 3.13.0 to before 3.13.15; 4.0.0 to before 4.0.20; 4.1.0 to before 4.1.11; 4.2.0 to before 4.2.6 Fixed in 3.13.15, 4.0.20, 4.1.11, 4.2.6 Patch available CNA

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:broadcom:rabbitmq_server:*:*:*:*:*:*:*:*3.13.0 to before 3.13.15; 4.0.0 to before 4.0.20; 4.1.0 to before 4.1.11; 4.2.0 to before 4.2.6VulnerableBroadcom
  • cpe:2.3:a:broadcom:rabbitmq_server:*:*:*:*:*:*:*:* Versions 3.13.0 to before 3.13.15; 4.0.0 to before 4.0.20; 4.1.0 to before 4.1.11; 4.2.0 to before 4.2.6 Vulnerable ·Broadcom

Remediation

  • Fix · CNA rabbitmq-server (rabbitmq) Fixed in 3.13.15, 4.0.20, 4.1.11, 4.2.6

Red Hat 1 advisory

  • RHSA-2026:67552 Released 2026-09-15 · Red Hat rating Important
    Red Hat Hardened Images RPMs bug fix and enhancement update
    • Red Hat Hardened Images rabbitmq-server4.3-4.3.6-1.hum1@aarch64, rabbitmq-server4.3-4.3.6-1.hum1@src, rabbitmq-server4.3-4.3.6-1.hum1@x86_64

Vendor assessments

Red Hat

Red Hat rating: Moderate. Red Hat's page for this CVE →

ProductStatusPlan or fix
Red Hat Hardened ImagesAffectedNo fix planned: Will not fix
Red Hat OpenStack Platform 13 (Queens)AffectedNo fix planned: Out of support scope
Red Hat OpenStack Platform 16.2AffectedNo fix planned: Out of support scope
Red Hat OpenStack Platform 17.1AffectedNo fix planned: Out of support scope
Red Hat OpenStack Platform 18.0AffectedNo fix yet: Fix deferred
Red Hat Hardened ImagesFixed RHSA-2026:67552

Timeline

  1. 2026-10-02 Threatist record created from CVE-2026-67225
  2. 2026-10-18 Fix available: RHSA-2026:67552 · Red Hat
  3. 2026-10-18 Fix available: Red Hat Hardened Images · Red Hat
  4. 2026-10-18 CVSS score added · Red Hat
  5. 2026-10-20 CVSS score added · NVD

References

  • TI-2026-41154 Improper authentication in rabbitmq-server CVSS 3.1CRITICAL 10.0
  • TI-2026-41149 RabbitMQ: UNC SSRF affecting the management UI on Windows CVSS 3.1CRITICAL 10.0
  • TI-2026-41158 Resource allocation without limits in rabbitmq-server CVSS 3.1HIGH 7.5
  • TI-2026-47695 RabbitMQ: OAuth2 Client Secret Exposed via Unauthenticated JavaScript Endpoint CVSS 4.0HIGH 8.2
  • TI-2026-47694 RabbitMQ: JWKS Fetch Ignores HTTP Response Status Code - Signing Key Destruction Causes Authentication DoS CVSS 4.0HIGH 8.2
  • TI-2026-45167 RabbitMQ Java client: Unvalidated Class.forName in JSON-RPC ProcedureDescription enables arbitrary class loading CVSS 4.0HIGH 7.5
See all 100 →

Sources