CVE-2026-41714 — spring-amqp
MEDIUMCVE-2026-41714 is a medium-severity (CVSS 4) CWE-295 vulnerability in org.springframework.amqp:spring-amqp. A fix is available for org.springframework.amqp:spring-amqp — see the affected versions and patch details below.
In Spring AMQP the RabbitConnectionFactoryBean.setUri("amqps://...") bypasses secure SSL setup, uses TrustEverythingTrustManager
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-41714.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-41714 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 379,842 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
org.springframework.amqp:spring-amqp☕org.springframework.amqp:spring-amqp☕org.springframework.amqp:spring-amqp☕org.springframework.amqp:spring-amqpReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Applications that configure their broker connection via RabbitConnectionFactoryBean.setUri("amqps://...") without also calling setUseSSL(true) get TLS encryption with no certificate validation and no hostname verification.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework.amqp:spring-amqp | ≥ 4.0.0&&< 4.0.4 | 4.0.4org.springframework.amqp:spring-amqp:4.0.4 |
| ☕Maven | org.springframework.amqp:spring-amqp | ≥ 3.2.0&&< 3.2.11 | 3.2.11org.springframework.amqp:spring-amqp:3.2.11 |
| ☕Maven | org.springframework.amqp:spring-amqp | ≥ 3.1.0 | No fix |
| ☕Maven | org.springframework.amqp:spring-amqp | all versions | No fix |
Affected Products
spring advanced message queuing protocolvmwareDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.amqp:spring-amqp, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework.amqp:spring-amqp to 4.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-41714 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Red Hat products that bundle Spring AMQP are affected by this flaw. However, exploitation requires the application to use the specific pattern of calling RabbitConnectionFactoryBean.setUri() with an amqps:// URI without also calling setUseSSL(true), and the attacker must be in a Man-in-the-Middle position on the…
When using RabbitConnectionFactoryBean.setUri() with an amqps:// URI, explicitly call setUseSSL(true) to enable proper certificate validation and hostname verification.Source: Red Hat security advisory for CVE-2026-41714 (CC BY 4.0)
Frequently Asked Questions
Is CVE-2026-41714 in your dependencies?
Find it across Maven, including transitive dependencies.