CVE-2026-44393: OpenStack oslo.messaging does not verify RabbitMQ broker hostname during TLS handshake
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 sslcafile is configured, the driver enables certificate chain validation but does not pass the expected broker hostname into the underlying TLS stack.
Published Jun 4, 2026 · Updated Jul 15, 2026
Affected packages
oslo.messaging
- Ecosystem
- PyPI
- Affected
- >= 1.0.0, <= 17.3.0
- Fixed in
- No patched version yet
- Check
pip show oslo.messaging
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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.
References
- https://nvd.nist.gov/vuln/detail/CVE-2026-44393
- https://bugs.launchpad.net/oslo.messaging/+bug/2150316
- https://wiki.openstack.org/wiki/OSSN/OSSN-0096
- https://access.redhat.com/security/cve/CVE-2026-44393
- https://bugzilla.redhat.com/show_bug.cgi?id=2484835
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-44393.json
- https://github.com/advisories/GHSA-76qh-xr7q-h39m
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
