CVE-2026-41714
Description
A flaw was found in Spring AMQP. Applications that configure their broker connection using RabbitConnectionFactoryBean.setUri("amqps://...") without explicitly enabling SSL via setUseSSL(true) may establish a TLS (Transport Layer Security) encrypted connection without proper certificate validation or hostname verification. This oversight could allow a remote attacker to intercept and potentially read sensitive information by performing a Man-in-the-Middle attack.
Statement
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 network path to the RabbitMQ broker.
Mitigation
When using RabbitConnectionFactoryBean.setUri() with an amqps:// URI, explicitly call setUseSSL(true) to enable proper certificate validation and hostname verification.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.9 | N/A | 4 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | High | N/A | High |
| Privileges Required | None | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Changed |
| Confidentiality | High | N/A | Low |
| Integrity Impact | None | N/A | None |
| Availability Impact | None | N/A | None |
Vector
Red Hat: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
cve.org: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N
Understanding the Weakness (CWE)
Integrity,Authentication
Technical Impact: Bypass Protection Mechanism; Gain Privileges or Assume Identity
When a certificate is invalid or malicious, it might allow an attacker to spoof a trusted entity by interfering in the communication path between the host and client. The product might connect to a malicious host while believing it is a trusted host, or the product might be deceived into accepting spoofed data that appears to originate from a trusted host.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
