CVE-2026-47860: Unbounded decompression of attacker-supplied compressed message bodies
An attacker who can publish to a queue consumed by an application that has enabled message decompression can crash the consumer JVM with a single ~1 MB message. Spring AMQP 4.1.0 Spring AMQP 4.0.0 - 4.0.4 Spring AMQP 3.2.0 - 3.2.12 Spring AMQP 2.4.18 and earlier
Affected Software
Event History
Frequently Asked Questions
Which deployments are exposed to this issue?
Applications using Spring AMQP are exposed when they consume from a queue, have message decompression enabled, and an attacker can publish messages to that queue. The issue affects Spring AMQP 4.1.0, 4.0.0 through 4.0.4, 3.2.0 through 3.2.12, and 2.4.18 and earlier.
What level of access does an attacker need?
The attacker needs privileges to publish to a queue consumed by the target application. No user interaction is required, and a single attacker-supplied compressed message of approximately 1 MB can crash the consumer JVM.
Are applications using the default configuration affected?
The provided information identifies message decompression as a required condition. It does not state whether message decompression is enabled by default.
What can be done if an upgrade cannot be applied immediately?
Disable message decompression where possible and restrict publishing permissions on queues consumed by affected applications. Prioritize queues to which untrusted or broadly privileged publishers have access.