CVE-2026-47860

Analyzed Analyzed - Analysis Complete

Denial of Service in Spring AMQP via Message Decompression

Publication date: 2026-08-27

Last updated on: 2026-09-02

Assigner: VMware

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

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-08-27

Last Modified

2026-09-02

Generated

2026-09-16

AI Q&A

2026-08-27

EPSS Evaluated

2026-09-15

NVD

CVE-2026-47860

EUVD

EUVD-2026-66826

Affected Vendors & Products

Vendor	Product	Version / Range
vmware	spring_advanced_message_queuing_protocol	to 2.4.19 (exc)
vmware	spring_advanced_message_queuing_protocol	From 3.2.0 (inc) to 3.2.13 (exc)
vmware	spring_advanced_message_queuing_protocol	From 4.0.0 (inc) to 4.0.4.1 (exc)
vmware	spring_advanced_message_queuing_protocol	From 4.1.0 (inc) to 4.1.0.1 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-835	The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop.

Attack-Flow Graph

Executive Summary

This vulnerability allows an attacker who can publish to a queue consumed by an application to crash the consumer JVM by sending a single compressed message around 1 MB in size. The issue stems from unbounded decompression of attacker-supplied compressed message bodies.

Detection Guidance

Monitor for application crashes or JVM terminations after receiving messages. Check logs for OutOfMemoryError or System.exit(99) events. Inspect message queues for unusually large messages (~1 MB) with compressed payloads.

Impact Analysis

An attacker could exploit this to cause a denial of service by crashing the application repeatedly. The default error handler terminates the JVM with System.exit(99) on OutOfMemoryError, and redelivery on restart can lead to continuous crashes until manually purged.

Compliance Impact

This vulnerability could indirectly impact compliance with GDPR or HIPAA by causing service disruptions due to application crashes. A crash-loop scenario may lead to prolonged downtime, potentially affecting data processing or availability requirements under these regulations.

Mitigation Strategies

Upgrade to fixed versions of Spring AMQP: 4.1.1 OSS, 4.0.5 OSS, 3.2.13, or 2.4.19 (Enterprise Support Only). No additional mitigation steps are required beyond upgrading.

Hi! I’m here to help you understand CVE-2026-47860. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70