CVE-2026-44393: n/a
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.
AI Analysis
Technical Summary
CVE-2026-44393 affects OpenStack oslo.messaging RabbitMQ driver versions 1.0.0 through 17.3.0. The vulnerability arises because the driver enables certificate chain validation when ssl_ca_file is configured but fails to perform TLS hostname verification by not passing the expected broker hostname to the TLS stack. This flaw allows an attacker capable of intercepting control-plane traffic to impersonate the RabbitMQ broker using any certificate signed by the deployment CA, facilitating man-in-the-middle attacks on RPC and notification traffic within OpenStack services using oslo.messaging with RabbitMQ over TLS.
Potential Impact
An attacker who can intercept control-plane traffic can impersonate the RabbitMQ message broker by presenting any certificate signed by the deployment CA, bypassing hostname verification. This compromises the confidentiality and integrity of RPC and notification traffic between OpenStack services, potentially leading to unauthorized data access or manipulation. Availability is not impacted.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The Red Hat advisory linked does not specify an official fix or workaround at this time. Users should monitor the vendor advisory for updates and consider additional network-level protections to prevent interception of control-plane traffic until a fix is available.
CVE-2026-44393: n/a
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 v3.1
Score 7.4high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-44393 affects OpenStack oslo.messaging RabbitMQ driver versions 1.0.0 through 17.3.0. The vulnerability arises because the driver enables certificate chain validation when ssl_ca_file is configured but fails to perform TLS hostname verification by not passing the expected broker hostname to the TLS stack. This flaw allows an attacker capable of intercepting control-plane traffic to impersonate the RabbitMQ broker using any certificate signed by the deployment CA, facilitating man-in-the-middle attacks on RPC and notification traffic within OpenStack services using oslo.messaging with RabbitMQ over TLS.
Potential Impact
An attacker who can intercept control-plane traffic can impersonate the RabbitMQ message broker by presenting any certificate signed by the deployment CA, bypassing hostname verification. This compromises the confidentiality and integrity of RPC and notification traffic between OpenStack services, potentially leading to unauthorized data access or manipulation. Availability is not impacted.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The Red Hat advisory linked does not specify an official fix or workaround at this time. Users should monitor the vendor advisory for updates and consider additional network-level protections to prevent interception of control-plane traffic until a fix is available.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- mitre
- Date Reserved
- 2026-05-05T00:00:00.000Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
- Vendor Advisory Urls
- [{"url":"https://access.redhat.com/security/cve/CVE-2026-44393","vendor":"Red Hat"}]
Threat ID: 6a219e6ae29bf47b50b4476a
Added to database: 06/04/2026, 15:48:58 UTC
Last enriched: 07/15/2026, 09:22:09 UTC
Last updated: 07/31/2026, 19:22:59 UTC
Views: 66
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.