Vulnerability Description
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.
CVSS Score
HIGH
Related Weaknesses (CWE)
References
- https://bugs.launchpad.net/oslo.messaging/+bug/2150316
- https://wiki.openstack.org/wiki/OSSN/OSSN-0096
- https://access.redhat.com/errata/RHSA-2026:54757
- 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
FAQ
What is CVE-2026-44393?
CVE-2026-44393 is a vulnerability with a CVSS score of 7.4 (HIGH). 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_...
How severe is CVE-2026-44393?
CVE-2026-44393 has been rated HIGH with a CVSS base score of 7.4/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-44393?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.