How severe is CVE-2026-59320?

CVE-2026-59320 has a CVSS 3.x base score of 6.5, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.

Is CVE-2026-59320 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (34th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-59320?

CVE-2026-59320 affects Vmware Spring Advanced Message Queuing Protocol. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-59320?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2026-59320 published?

CVE-2026-59320 was published on 2026-08-27 and last updated on 2026-08-31.

CVE-2026-59320

CVE-2026-59320 is a medium-severity vulnerability in Vmware Spring Advanced Message Queuing Protocol with a CVSS 3.x base score of 6.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-772.

Key facts

Severity: Medium (CVSS 3.x base score 6.5)
EPSS exploit prediction: 0% (34th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-772
Affected product: Vmware Spring Advanced Message Queuing Protocol
Published: 2026-08-27
Last modified: 2026-08-31

Description

When a container-level ErrorHandler is configured (the mitigation for finding 221000), each delivery whose processing throws still permanently consumes one link credit. After initialCredits (default 100) failing messages the receiver's credit reaches zero and the broker stops delivering, leaving the listener silently stalled while isRunning() remains true. Spring AMQP 4.1.0

Frequently asked questions

What is CVE-2026-59320?: When a container-level ErrorHandler is configured (the mitigation for finding 221000), each delivery whose processing throws still permanently consumes one link credit. After initialCredits (default 100) failing messages the receiver's credit reaches zero and the broker stops delivering, leaving the listener silently stalled while isRunning() remains true. Spring AMQP 4.1.0
How severe is CVE-2026-59320?: CVE-2026-59320 has a CVSS 3.x base score of 6.5, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
Is CVE-2026-59320 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (34th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-59320?: CVE-2026-59320 affects Vmware Spring Advanced Message Queuing Protocol. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-59320?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2026-59320 published?: CVE-2026-59320 was published on 2026-08-27 and last updated on 2026-08-31.

References

https://spring.io/security/cve-2026-59320

Affected products (1)

cpe:2.3:a:vmware:spring_advanced_message_queuing_protocol:*:*:*:*:*:*:*:*

More vulnerabilities in Vmware Spring Advanced Message Queuing Protocol

CVE-2016-2173 — Critical (CVSS 9.8): org.springframework.core.serializer.DefaultDeserializer in Spring AMQP before 1.5.5 allows remote attackers to execute…
CVE-2026-59272 — Medium (CVSS 6.8): Any application shipping logs to RabbitMQ over TLS via the Log4j2 appender, relying on the documented default, is…
CVE-2026-59275 — Medium (CVSS 6.6): A single hostile AMQP message can terminate the entire consumer JVM (System.exit(99)), not just the listener thread —…
CVE-2026-47860 — Medium (CVSS 6.5): An attacker who can publish to a queue consumed by an application that has enabled message decompression can crash the…
CVE-2021-22095 — Medium (CVSS 6.5): In Spring AMQP versions 2.2.0 - 2.2.19 and 2.3.0 - 2.3.11, the Spring AMQP Message object, in its toString() method,…
CVE-2021-22097 — Medium (CVSS 6.5): In Spring AMQP versions 2.2.0 - 2.2.18 and 2.3.0 - 2.3.10, the Spring AMQP Message object, in its toString() method,…

All CVEs affecting Vmware Spring Advanced Message Queuing Protocol →

Other CWE-772 vulnerabilities

CVE-2020-12134 — Critical (CVSS 9.8): Nanometrics Centaur through 4.3.23 and TitanSMA through 4.2.20 mishandle access control for the syslog log.
CVE-2017-15032 — Critical (CVSS 9.8): ImageMagick version 7.0.7-2 contains a memory leak in ReadYCBCRImage in coders/ycbcr.c.
CVE-2017-14138 — Critical (CVSS 9.8): ImageMagick 7.0.6-5 has a memory leak vulnerability in ReadWEBPImage in coders/webp.c because memory is not freed in…
CVE-2017-11641 — Critical (CVSS 9.8): GraphicsMagick 1.3.26 has a Memory Leak in the PersistCache function in magick/pixel_cache.c during writing of Magick…
CVE-2020-14339 — High (CVSS 8.8): A flaw was found in libvirt, where it leaked a file descriptor for `/dev/mapper/control` into the QEMU process. This…
CVE-2018-19760 — High (CVSS 8.8): cfg_init in confuse.c in libConfuse 3.2.2 has a memory leak.

Browse all CWE-772 vulnerabilities →