CVE Catalog

CVE-2026-44393

HighCVSS 7.4
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.17%

7th percentile - higher than 7% of all known CVEs

Summary

The RabbitMQ driver in oslo.messaging (versions 1.0.0 through 17.3.0) does not verify the TLS hostname when connecting to the broker. Even with ssl_ca_file configured, any certificate signed by the deployment CA is accepted, allowing an attacker to intercept traffic and perform man-in-the-middle attacks on RPC and notification traffic.

Risk Assessment

An attacker on the control-plane network can impersonate the RabbitMQ broker, intercepting and modifying sensitive data exchanged between OpenStack services.

Recommendation

Update oslo.messaging to version 17.3.1 or later, which includes the TLS hostname verification fix.

Related vulnerabilities

Original NVD description (English source)

An issue was discovered in OpenStack oslo.messaging 1.0.0 through 17.3.0. The oslo.messaging RabbitMQ driver does not perform TLS hostname verification when connecting to the message broker. When ssl_ca_file is configured, the driver enables certificate chain validation but does not pass the expected broker hostname into the underlying TLS stack. Any certificate signed by the deployment CA is accepted regardless of hostname, allowing an attacker who can intercept control-plane traffic to impersonate the RabbitMQ broker and perform a man-in-the-middle attack on RPC and notification traffic. All OpenStack services using oslo.messaging with RabbitMQ over TLS are affected.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS