CVE-2026-47860 json
Unbounded decompression of attacker-supplied compressed message bodies
published 2026-08-26 2 mo ago modified 2026-09-02 2 mo ago also EUVD-2026-66826
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 36%
- public exploits
- 0
- none known
Summary
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
Patch / fix
- vmware spring_advanced_message_queuing_protocol 2.4.19, 3.2.13, 4.0.4.1, 4.1.0.1
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-47860 updated cvss 6.5
org.springframework.amqp/spring-amqp: Spring AMQP: Denial of Service via unbounded decompression of compressed messages
-
Red Hat build of Apache Camel 4 for Quarkus 3 spring-amqp 3.2.9affected: workaround, no fix available “Fix deferred”
-
Red Hat Fuse 7 spring-amqp 3.2.9affected: workaround, no fix planned “Out of support scope”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 mo ago
Exploit prediction
0.42% chance of exploitation in the next 30 days, higher than 36% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Spring Spring AMQP
Classification
- Weakness
-
- CWE-835 Loop with Unreachable Exit Condition
References
-
spring.io
/security/cve-2026-47860
vendor-advisory
Sources
- CVE List CVE-2026-47860
- NVD CVE-2026-47860
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.