CVE-2026-41701 Overview
CVE-2026-41701 affects Spring AMQP, the Spring Framework module that integrates Java applications with RabbitMQ message brokers. The vulnerability resides in RabbitTemplate.sendAndReceive() when used with a fixed reply queue. Correlation IDs for replies are generated using a simple internal counter, making them predictable [CWE-330]. An attacker with access to the reply queue can guess valid correlation IDs and intercept or spoof reply messages. The flaw impacts Spring AMQP versions 4.0.0 through 4.0.3, 3.2.0 through 3.2.10, 3.1.0 through 3.1.15, and 2.4.0 through 2.4.17.
Critical Impact
Attackers with reply queue access can predict correlation IDs to intercept or inject responses, breaking the integrity of request-reply messaging.
Affected Products
- Spring AMQP 4.0.0 through 4.0.3
- Spring AMQP 3.2.0 through 3.2.10, 3.1.0 through 3.1.15
- Spring AMQP 2.4.0 through 2.4.17
Discovery Timeline
- 2026-06-10 - CVE-2026-41701 published to NVD
- 2026-06-10 - Last updated in NVD database
Technical Details for CVE-2026-41701
Vulnerability Analysis
The Spring AMQP RabbitTemplate class supports a request-reply pattern through sendAndReceive(). When configured with a fixed reply queue, the template generates a correlation ID for each outgoing message and matches incoming replies against pending requests using that identifier. The vulnerability stems from how this correlation ID is produced. Instead of using a cryptographically secure random value, the implementation relies on an internal monotonic counter. An attacker who can observe or enumerate correlation IDs can predict future values used by legitimate publishers. This breaks the implicit trust boundary between request and reply, classified as Use of Insufficiently Random Values [CWE-330].
Root Cause
The root cause is the use of a deterministic counter rather than a secure random source for correlation ID generation in the fixed reply queue code path. Predictability allows an attacker to reason about which value will be assigned next.
Attack Vector
Exploitation requires high privileges and high attack complexity over a network path. An attacker with permission to publish to the shared reply queue can craft a message carrying a predicted correlation ID. The forged reply may be consumed by RabbitTemplate and returned to the calling application as if it were the legitimate broker response. This compromises confidentiality and integrity of the request-reply exchange across a changed security scope.
No verified exploit code is publicly available. See the Spring Security Advisory CVE-2026-41701 for additional technical context.
Detection Methods for CVE-2026-41701
Indicators of Compromise
- Reply messages on a fixed reply queue carrying correlation IDs that do not match any outstanding request issued by the application.
- Unexpected duplicate or out-of-order replies processed by RabbitTemplate.sendAndReceive() callers.
- Application logs showing reply handling for requests that have already been completed or timed out.
Detection Strategies
- Inventory all Java services using Spring AMQP and identify versions in the vulnerable ranges via dependency scanning of pom.xml and build.gradle manifests.
- Audit RabbitMQ broker permissions to enumerate every principal authorized to publish to fixed reply queues.
- Inspect broker message traces for low-entropy, sequential correlation ID patterns indicative of the counter-based generator.
Monitoring Recommendations
- Log and alert on publish operations to reply queues originating from any identity other than the intended request issuer.
- Track RabbitTemplate reply timeouts and mismatched correlation events as anomaly signals.
- Forward broker authentication and authorization events to a centralized analytics platform for correlation with application-layer reply mismatches.
How to Mitigate CVE-2026-41701
Immediate Actions Required
- Upgrade Spring AMQP to a fixed release per the Spring Security Advisory CVE-2026-41701.
- Restrict publish permissions on fixed reply queues to only the application instances that own them.
- Review and rotate any RabbitMQ credentials shared across services that use fixed reply queues.
Patch Information
VMware/Spring released fixed versions addressing the predictable correlation ID generator in RabbitTemplate.sendAndReceive(). Consult the Spring Security Advisory CVE-2026-41701 for the exact patched version corresponding to each maintained branch (2.4.x, 3.1.x, 3.2.x, and 4.0.x).
Workarounds
- Switch from the fixed reply queue strategy to temporary, exclusive, auto-delete reply queues per request, which scopes correlation to a single consumer.
- Apply broker-level access control lists so that only the publishing service can write to its own reply queue.
- Enforce TLS and per-service credentials on RabbitMQ connections to reduce the population of principals able to reach the reply queue.
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
