Reply poisoning via sequential correlation ID generation
Published Jun 9, 2026 · Updated Jun 9, 2026
Reply poisoning in Spring AMQP allows remote authenticated users to inject unauthorized replies through a fixed reply queue. RabbitTemplate.sendAndReceive() assigns messageTag correlation IDs from a simple sequential counter instead of unpredictable values, allowing a guessed tag to bind an attacker-supplied reply to a pending request. Exploitation requires high broker privileges and winning a timing race before the legitimate reply; success exposes request-associated data or causes the application to process attacker-controlled content.
Summary
What happened
Reply poisoning in Spring AMQP allows remote authenticated users to inject unauthorized replies through a fixed reply queue. RabbitTemplate.sendAndReceive() assigns messageTag correlation IDs from a simple sequential counter instead of unpredictable values, allowing a guessed tag to bind an attacker-supplied reply to a pending request. Exploitation requires high broker privileges and winning a timing race before the legitimate reply; success exposes request-associated data or causes the application to process attacker-controlled content.
The record
- CVE
- CVE-2026-41701
- Published
- Jun 9, 2026
- Updated
- Jun 9, 2026
- Vendor
- Spring
- Product
- Spring AMQP
- Classifications
- CWE-330, T1565.002
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 9, 2026CVE publishedPublication date reported by the CVE source.
- Jun 9, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.4.0 <2.4.18
- Affected versionversion=3.1.0 <3.1.16
- Affected versionversion=3.2.0 <3.2.11
- Affected versionversion=4.0.0 <4.0.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo