Is CVE-2026-41701 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-41701 being exploited in the wild.

How severe is CVE-2026-41701?

Medium severity, with a CVSS score of 4.4, published 10 June 2026.

Which products and versions are affected?

org.springframework.amqp:spring-amqp (Maven) ECOSYSTEM:introduced=4.0.0,fixed=4.0.4; VMware Spring AMQP 4.0.0 through 4.0.3; 3.2.0 through 3.2.10; 3.1.0 through 3.1.15; 2.4.0 through 2.4.17, 4.0.0 to 4.0.3, 3.2.0 to 3.2.10, 3.1.0 to 3.1.15, 2.4.0 to 2.4.17.

Is there a fix for CVE-2026-41701?

Yes. org.springframework.amqp:spring-amqp (Maven): upgrade to 4.0.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-41701 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-41701?

Check whether you run org.springframework.amqp:spring-amqp (Maven) or VMware Spring AMQP at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-41701: VMware Spring AMQP predictable Correlation IDs in RabbitTemplate

CVE-2026-41701 · Severity: medium · CVSS 4.4 · Published 2026-06-10

Spring AMQP is a library used by Java applications to communicate with RabbitMQ message brokers. A security flaw in how the library tracks message replies makes it possible for an attacker to predict the ID of a pending response. This could allow an unauthorized party to inject a fake response or intercept data, potentially disrupting business workflows or compromising the integrity of automated tasks.

Technologies: org.springframework.amqp:spring-amqp (Maven), VMware Spring AMQP. Vendors: Maven, VMware.

Quick answers

Is CVE-2026-41701 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-41701 being exploited in the wild.
How severe is CVE-2026-41701?: Medium severity, with a CVSS score of 4.4, published 10 June 2026.
Which products and versions are affected?: org.springframework.amqp:spring-amqp (Maven) ECOSYSTEM:introduced=4.0.0,fixed=4.0.4; VMware Spring AMQP 4.0.0 through 4.0.3; 3.2.0 through 3.2.10; 3.1.0 through 3.1.15; 2.4.0 through 2.4.17, 4.0.0 to 4.0.3, 3.2.0 to 3.2.10, 3.1.0 to 3.1.15, 2.4.0 to 2.4.17.
Is there a fix for CVE-2026-41701?: Yes. org.springframework.amqp:spring-amqp (Maven): upgrade to 4.0.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-41701 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-41701?: Check whether you run org.springframework.amqp:spring-amqp (Maven) or VMware Spring AMQP at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

org.springframework.amqp:spring-amqp (Maven): upgrade to 4.0.4 or later

# set org.springframework.amqp:spring-amqp to 4.0.4 in your pom.xml or build.gradle

Technical details

The vulnerability exists in the RabbitTemplate.sendAndReceive() method of Spring AMQP when configured with a fixed reply queue. The root cause is the use of a predictable internal simple counter to generate correlation IDs for message replies, rather than a cryptographically secure random value. An attacker with sufficient privileges to publish messages to the broker could predict future correlation IDs and inject spoofed responses into the reply queue. This could lead to a loss of message integrity or unauthorized data exposure within the application's request-response cycle. The issue is addressed in versions 3.2.11 and 4.0.4.

Affected products

VMware Spring AMQP 4.0.0 to 4.0.3, 3.2.0 to 3.2.10, 3.1.0 to 3.1.15, 2.4.0 to 2.4.17

Identifiers

CVE-2026-41701
GHSA-p5f7-rjhp-pxvc

Timeline

2026-06-10: disclosed
2026-06-10: advisory
2026-08-12: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.