CVE-2026-44393
Description
A flaw was found in OpenStack oslo.messaging. The RabbitMQ driver does not properly verify the hostname of the message broker when establishing a TLS (Transport Layer Security) connection. An attacker capable of intercepting control-plane network traffic can exploit this vulnerability to impersonate the RabbitMQ broker. This allows the attacker to perform a man-in-the-middle attack, potentially leading to the disclosure or manipulation of sensitive RPC (Remote Procedure Call) and notification traffic.
Statement
This Important flaw in OpenStack oslo.messaging impacts Red Hat OpenStack Platform and OpenShift Container Platform when using RabbitMQ with TLS. The vulnerability arises from the RabbitMQ driver's failure to perform proper hostname verification during TLS connection establishment. This oversight enables an attacker capable of intercepting control-plane network traffic to impersonate the RabbitMQ broker, potentially leading to man-in-the-middle attacks that compromise the confidentiality and integrity of sensitive RPC and notification data.
Mitigation
To mitigate the risk of man-in-the-middle attacks, restrict network access to the RabbitMQ message broker. Configure firewall rules to permit inbound connections to the RabbitMQ port (typically 5672 or 5671 for AMQPS) only from authorized hosts and services within the control plane. This operational measure reduces the exposure to attackers attempting to intercept and impersonate the broker.
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).
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 7.4 | N/A | 7.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 | Unchanged |
| Confidentiality | High | N/A | High |
| Integrity Impact | High | N/A | High |
| 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:H/A:N
cve.org: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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.
