CVE-2026-41701
Description
Spring AMQP's predictable correlation IDs in RabbitTemplate.sendAndReceive() allow attackers to poison replies sent to fixed reply queues.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Spring AMQP's predictable correlation IDs in RabbitTemplate.sendAndReceive() allow attackers to poison replies sent to fixed reply queues.
Vulnerability
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 are affected by a vulnerability where the correlation IDs generated for replies in the RabbitTemplate.sendAndReceive() method with fixed reply queues are predictable due to an internal simple counter.
Exploitation
An attacker with network access to the RabbitMQ broker can exploit this vulnerability by observing the predictable correlation IDs and sending a malicious reply message to the fixed reply queue with a matching correlation ID. This requires the attacker to be able to interact with the RabbitMQ broker and potentially infer the timing of legitimate requests.
Impact
Successful exploitation allows an attacker to poison the reply queue by sending a crafted message with a predictable correlation ID. This can lead to the application processing an incorrect or malicious reply, potentially causing denial of service or allowing for further manipulation of application logic, depending on how the application handles the received reply.
Mitigation
This vulnerability is addressed in Spring AMQP. Please refer to the official Spring security advisory [1] for specific patched versions and release dates. It is recommended to update to a non-vulnerable version as soon as possible. No workarounds are disclosed in the available references.
AI Insight generated on Jun 10, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
1- Range: 4.0.0 - 4.0.3, 3.2.0 - 3.2.10, 3.1.0 - 3.1.15, 2.4.0 - 2.4.17
Patches
0No patches discovered yet.
Vulnerability mechanics
No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.
References
1News mentions
1- Spring Projects: 25 Vulnerabilities Disclosed, Including SpEL Injection and Deserialization FlawsVypr Intelligence · Jun 10, 2026