Man-in-the-middle interception via omitted TLS hostname check
Published Jun 4, 2026 · Updated Jun 4, 2026
Improper TLS hostname validation in OpenStack oslo.messaging 1.0.0 through 17.3.0 allows man-in-the-middle attackers to intercept RPC traffic. The RabbitMQ driver validates the broker certificate chain when ssl_ca_file is set but omits the expected broker hostname from the underlying TLS check. Exposure is limited to TLS-enabled RabbitMQ deployments; exploitation requires control-plane network access and a certificate trusted by the deployment CA.
Summary
What happened
Improper TLS hostname validation in OpenStack oslo.messaging 1.0.0 through 17.3.0 allows man-in-the-middle attackers to intercept RPC traffic. The RabbitMQ driver validates the broker certificate chain when ssl_ca_file is set but omits the expected broker hostname from the underlying TLS check. Exposure is limited to TLS-enabled RabbitMQ deployments; exploitation requires control-plane network access and a certificate trusted by the deployment CA.
The record
- CVE
- CVE-2026-44393
- Published
- Jun 4, 2026
- Updated
- Jun 4, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-295, CWE-297, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 4, 2026CVE publishedPublication date reported by the CVE source.
- Jun 4, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo