cve.bz

CVE-2026-41701 vmware spring advanced message queuing protocol: Use of Insufficiently Random Values

4.4 mediumEPSS 0.2%Fix available

Medium (4.4) in vmware spring advanced message queuing protocol. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in org.springframework.amqp:spring-amqp 3.2.11, 4.0.4.

On this page
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.

Severity

CVSS 3.1

4.4 medium
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 7th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-06-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-330 Use of Insufficiently Random Values
OWASP Top 10
A04:2025 Cryptographic Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-41701 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-41701?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-41701?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-41701 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-41701

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-41701](https://cve.bz/cve/badge/CVE-2026-41701.svg)](https://cve.bz/cve/CVE-2026-41701)

HTML:

<a href="https://cve.bz/cve/CVE-2026-41701"><img src="https://cve.bz/cve/badge/CVE-2026-41701.svg" alt="CVE-2026-41701"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Spring AMQPfrom 4.0.0 before 4.0.3.1
Spring AMQPfrom 3.2.0 before 3.2.10.1
Spring AMQPfrom 3.1.0 before 3.1.16
Spring AMQPfrom 2.4.0 before 2.4.18

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-p5f7-rjhp-pxvcMavenorg.springframework.amqp:spring-amqp>=4.0.0 <4.0.44.0.4
GHSA-p5f7-rjhp-pxvcMavenorg.springframework.amqp:spring-amqp>=3.2.0 <3.2.113.2.11
GHSA-p5f7-rjhp-pxvcMavenorg.springframework.amqp:spring-amqp>=3.1.0 <=3.1.15no fix published
GHSA-p5f7-rjhp-pxvcMavenorg.springframework.amqp:spring-amqp<=2.4.17no fix published

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

Red Hat products that bundle Spring AMQP are affected by this flaw. However, exploitation requires the application to use fixed reply queues rather than exclusive/auto-delete queues, and the attacker needs high privileges and network access to the RabbitMQ broker, significantly limiting practical exploitability.

ProductPackageStateAdvisory
Red Hat build of Apache Camel 4 for Quarkus 3spring-amqpFix deferred
Red Hat Fuse 7spring-amqpOut of support scope
Red Hat JBoss Enterprise Application Platform Expansion Packspring-amqpFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-41701.

Attack patterns (CAPEC)

  • CAPEC-59 Session Credential Falsification through Prediction Likelihood: High · Severity: High
  • CAPEC-112 Brute Force Severity: High
  • CAPEC-485 Signature Spoofing by Key Recreation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON