Description
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
Published: 2026-08-26
Score: 6.5 Medium
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability allows an attacker who can publish to a queue to send a specially crafted compressed message that the consumer application decompresses without proper bounds. This unbounded decompression consumes excessive memory and can cause the JVM to crash, resulting in a denial of service to the affected service. The underlying weakness is an unchecked resource exhaustion during decompression, as defined by CWE-400.

Affected Systems

Spring AMQP is affected in versions 4.1.0, 4.0.0 through 4.0.4, 3.2.0 through 3.2.12, and 2.4.18 and earlier. The flaw exists in the message consumer component that handles compressed message bodies.

Risk and Exploitability

The CVSS score of 6.5 indicates a moderate severity, but the exploit requires the attacker to have the ability to publish to the target queue, which may limit its reach to applications with exposed or insufficiently protected message brokers. The EPSS score is currently not available, and the vulnerability is not listed in the CISA KEV catalog. Because the attack vector is likely an authenticated or misconfigured publisher, the overall risk depends largely on the access controls of the message system. Once a patched or mitigated system is compromised, the application may experience repeated service interruptions from message-induced JVM crashes.

Generated by OpenCVE AI on August 27, 2026 at 01:22 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Spring AMQP to the latest stable release (4.1.1 or newer) which removes the unbounded decompression logic.
  • If an immediate upgrade is not possible, disable automatic decompression of message bodies in the Spring AMQP configuration or validate the size of incoming compressed messages before processing.
  • Apply general best practices for the Java Virtual Machine: configure adequate heap limits, enable OOM detection, and monitor for sudden memory consumption spikes to pre‑empt service disruptions.

Generated by OpenCVE AI on August 27, 2026 at 01:22 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

References
History

Thu, 27 Aug 2026 01:45:00 +0000

Type Values Removed Values Added
First Time appeared Spring
Spring spring Amqp
Weaknesses CWE-400
Vendors & Products Spring
Spring spring Amqp

Thu, 27 Aug 2026 00:30:00 +0000

Type Values Removed Values Added
Description 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
Title Unbounded decompression of attacker-supplied compressed message bodies
References
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}


Subscriptions

Spring Spring Amqp
cve-icon MITRE

Status: PUBLISHED

Assigner: vmware

Published:

Updated: 2026-08-26T23:28:46.607Z

Reserved: 2026-05-20T10:00:55.156Z

Link: CVE-2026-47860

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-27T01:17:33.000

Modified: 2026-08-27T01:17:33.000

Link: CVE-2026-47860

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-27T01:30:13Z

Weaknesses
  • CWE-400

    Uncontrolled Resource Consumption