CVE-2026-67225
CVE.org · Published
- Record status
- Published
- Identifier year (not publication year)
- 2026
- Source publication
- Source updated
- Imported by cveboard
- Source snapshot
- cve_2026-10-24_midnight_baseline ·
CNA source text (English)
RabbitMQ: Stream-protocol frame length never validated against frame_max
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.
Scoped product and version facts
Fix information unknown; no fixed version is derived here. Missing information does not prove that no fix exists.
Exploitation unknown; this catalogue does not assess exploitation.
rabbitmq-server
- Vendor
- rabbitmq
- Product
- rabbitmq-server
- Platforms
- Unknown
- Default status
Unknown
| Version (version) | Status (status) | Version scheme (versionType) | Exclusive end (lessThan) | Inclusive end (lessThanOrEqual) | Status changes (at → status) |
|---|---|---|---|---|---|
| >= 3.13.0, < 3.13.15 | affected | Unavailable | Unavailable | Unavailable | None listed |
| >= 4.0.0, < 4.0.20 | affected | Unavailable | Unavailable | Unavailable | None listed |
| >= 4.1.0, < 4.1.11 | affected | Unavailable | Unavailable | Unavailable | None listed |
| >= 4.2.0, < 4.2.6 | affected | Unavailable | Unavailable | Unavailable | None listed |