CVE-2026-41701: In Spring AMQP sequential correlation IDs enable reply poisoning on fixed reply queues
Noroxi assessment
Priority: Monitor (action score 17/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: org.springframework.amqp:spring-amqp (Maven) 3.2.11, 4.0.4.
Low priority for now. Upgrade to org.springframework.amqp:spring-amqp (Maven) 3.2.11, 4.0.4 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Correlation IDs for replies in the RabbitTemplate.sendAndReceive() with the fixed reply queue are predictable due to internal simple counter. Affected versions: 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.
- Published
- Jun 10, 2026
- Updated
- Oct 1, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- CWE-330
Report tools
Action score
17
Monitor
Low priority for now.
- CVSS
- 17 / 40 · 4.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · vmware
- 4.4
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| vmware | spring advanced message queuing protocol | cpe:2.3:a:vmware:spring_advanced_message_queuing_protocol |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- vmware spring advanced message queuing protocolbefore 2.4.18
- vmware spring advanced message queuing protocol3.1.0 and later · before 3.1.16
- vmware spring advanced message queuing protocol3.2.0 and later · before 3.2.10.1
- vmware spring advanced message queuing protocol4.0.0 and later · before 4.0.3.1
Versions reported by the vendor
Affected version ranges reported by the assigning authority (vmware). Independent of NVD's CPE analysis and usually ahead of it.
Spring Spring AMQP
- 4.0.0 and later · before 4.0.3.1affected
- 3.2.0 and later · before 3.2.10.1affected
- 3.1.0 and later · before 3.1.16affected
- 2.4.0 and later · before 2.4.18affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Maven | org.springframework.amqp:spring-amqp | from 3.1.0 · up to and including 3.1.15 | — |
| Maven | org.springframework.amqp:spring-amqp | from 3.2.0 · before 3.2.11 | 3.2.11 |
| Maven | org.springframework.amqp:spring-amqp | from 4.0.0 · before 4.0.4 | 4.0.4 |
| Maven | org.springframework.amqp:spring-amqp | up to and including 2.4.17 | — |
Same product
vmware: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-59272Log4j2 AmqpAppender disables TLS hostname verification by default27Monitor
- CVE-2026-59320In Spring AMQP the link credit never replenished on listener exception path26Monitor
- CVE-2026-59271Admin password disclosed in BrokerNotAliveException message26Monitor
Published before and after this one in the same product
- ← EarlierCVE-2023-34050Oct 19, 2023 · Spring AMQP Deserialization Vulnerability18Monitor
- ← EarlierCVE-2026-41714Jun 9, 2026 · In Spring AMQP the RabbitConnectionFactoryBean.setUri("amqps://...") bypasses secure SSL setup, uses TrustEverythingTrustManager16Monitor
- Later →CVE-2026-47860Aug 26, 2026 · Unbounded decompression of attacker-supplied compressed message bodies26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Maven:org.springframework.amqp:spring-amqp | 3.2.11 | Package registry (OSV) |
| Maven:org.springframework.amqp:spring-amqp | 4.0.4 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- Administrator privileges are required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-330 · Use of Insufficiently Random ValuesCVSS vector
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.