CVE-2026-44393
An issue was discovered in OpenStack oslo.messaging 1.0.0 through …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- bugs.launchpad.net/oslo.messaging/+bug/2150316
- wiki.openstack.org/wiki/OSSN/OSSN-0096
- access.redhat.com/security/cve/CVE-2026-44393
- bugzilla.redhat.com/show_bug.cgi?id=2484835
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-44393.json
- nvd.nist.gov/vuln/detail/CVE-2026-44393
- github.com/advisories/GHSA-76qh-xr7q-h39m
- access.redhat.com/errata/RHSA-2026:54757
- nvd.nist.gov/vuln/detail/CVE-2026-44393
- cve.org/CVERecord?id=CVE-2026-44393
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.